feat: add allow version not found parameter

[demeyerthom]

This pull request introduces code improvements and new functionality to enhance maintainability and flexibility. The most important changes include enforcing consistent formatting, adding a new input parameter allowComponentNotFound, and updating the MCC client to handle missing components gracefully.

Code Formatting and Consistency:

• Added semicolons to ensure consistent formatting across the src/check.ts file. [1] [2] [3] [4]
• Reformatted multi-line expressions for better readability, such as the dependencies mapping in getTurboChangedPackages.
• Updated environment variable values in getTurboPlan to use double quotes for consistency.

New Input Parameter:

• Added a new allowComponentNotFound boolean input to the Inputs type and updated the readInputs function to read this value from the workflow inputs. [1] [2]
• Passed the allowComponentNotFound parameter to the getLatestVersion method in src/main.ts.

MCC Client Enhancements:

• Updated the getLatestVersion method in the MCC client to accept the allowComponentNotFound parameter.
• Added logic to handle 404 errors gracefully when allowComponentNotFound is true, logging a warning instead of throwing an error.

[tleguijt]

shouldn't the default just be true?
It won't break any of the existing functionality I suppose

[demeyerthom]

It might cause some unexpected side effect. Without it will just pipe down the error to a later stage when building and registering the component happens. This would probably break in a run on main instead. That is obviously fixable by adding the --create-component flag in mach, but I don't know if we want that to happen as a default now?