Make "init not called" a configuration error

[henrymercer]

This error happens when analyze, autobuild, or resolve-environment is called before init.

Risk assessment

For internal use only. Please select the risk level of this change:

• Low risk: Changes are fully under feature flags, or have been fully tested and validated in pre-production environments and are highly observable, or are documentation or test only.
• High risk: Changes are not fully under feature flags, have limited visibility and/or cannot be tested outside of production.

Merge / deployment checklist

• Confirm this change is backwards compatible with existing workflows.
• Consider adding a changelog entry for this change.
• Confirm the readme and docs have been updated if necessary.

[Copilot]

Pull Request Overview

This PR changes the error type for "init not called" scenarios from a generic Error to a more specific ConfigurationError. This affects three action files that check if the config file exists before proceeding.

• Updates error handling to use ConfigurationError instead of generic Error for better error categorization
• Adds necessary imports for ConfigurationError in the affected TypeScript files
• Maintains the same error message to preserve existing behavior

Reviewed Changes

Copilot reviewed 6 out of 9 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
src/resolve-environment-action.ts	Imports ConfigurationError and uses it for config not found error
src/autobuild-action.ts	Imports ConfigurationError and uses it for config not found error
src/analyze-action.ts	Uses util.ConfigurationError for config not found error
lib/resolve-environment-action.js	Generated JavaScript code reflecting TypeScript changes
lib/autobuild-action.js	Generated JavaScript code reflecting TypeScript changes
lib/analyze-action.js	Generated JavaScript code reflecting TypeScript changes

---

_{You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.}

[mbg]

LGTM. Would it make sense to add this logic to a wrapper around getConfig? E.g. getRequiredConfig or something, since it's re-used in a few places?

[henrymercer]

Agreed, but I'll leave that as future work.