fix: handle invalid directory errors when creating atomic component

[dmbrooke]

KIT-2722

Unfortunately adding to the pile that is CDX-1428, but I couldn't find any simple/quick way to share the error class and behaviour between packages without doing larger changes.

Proposed changes

It would be useful to provide a helpful error message when attempting to create an atomic component in an invalid directory. Thus, I added the necessary to the create-atomic-component and create-atomic-result-component packages.

Testing

UNIT TESTS ARE STILL IN PROGRESS. For now, you can test the changes by following these steps:

• Build this branch (npm run build)
• Open a non-node project directory in your terminal (e.g., a java project)
• Try to create a component in said directory using your local build.
  • If the directory is adjacent to where you have cloned the CLI project, your command will look something like

  ../cli/packages/cli/core/bin/dev atomic:cmp --type=result test-result-component
  

• Confirm that a clear error message outputs in your terminal, explaining that the current directory is invalid.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues found.

Snapshot Warnings

⚠️: No snapshots were found for the head SHA 2ba4317.

Ensure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice.

Scanned Manifest Files

[github-actions]

Thanks for your contribution @dmbrooke !
When your pull-request is ready to be merged, check the box below to merge it

• Merge!

[github-actions]

Pull Request Report

PR Title

✅ Title follows the conventional commit spec.

[y-lakhdar]

Suggested change

	'Current working directory is either not empty or not an npm project (no package.json found). Please try again in an empty directory.'
	'Current working directory is either not empty or not an npm project (no package.json found). Please try again in a valid project'

maybe specifying how to initialize an atomic project

[mrrajamanickam-coveo]

Maybe link to some relevant doc which explains the process e.g https://docs.coveo.com/en/cli/ or something more specific if available

[louis-bompart]

Disagreeing here: The create-atomic-(result)-component packages are initializers that are agnostic of the concept of atomic project.
i.e. you can use them without an atomic project.

[dmbrooke]

I personally think it's valid to refer to it as a valid project as that isn't specific to an atomic project. I think I'll update the link for this description to instead point to the atomic:cmp command documentation as it clearly outlines in what contexts the command will work:
https://docs.coveo.com/en/cli/#coveo-atomiccmp-name

[mrrajamanickam-coveo]

Maybe link to some relevant doc which explains the process e.g https://docs.coveo.com/en/cli/ or something more specific if available