This pull request introduces a new --force flag for Firebase deployments, enabling users to force deploy changes that may increase their billing, such as deploying more than 0 minimum instances of a function. The changes include updates to the deployment logic, input handling, and test coverage.

Reasoning:

• If you attempt to modify the 'minimum required instance' value from anything other than 0 then you encounter an error. This '--force' flag bypasses the error.

Enhancements to Deployment Functionality:

• Added a force input in action.yml to accept the --force flag for deployments. This input is optional and defaults to false.
• Introduced a new deployWithForce function in src/deploy.ts to handle deployments with the --force flag, including parsing its result.
• Updated existing deployment functions (deployPreview and deployProductionSite) to support the force option in their configurations. [1] [2]

Codebase Updates for --force Support:

• Updated execWithCredentials in src/deploy.ts to append the --force flag to Firebase CLI commands when the force option is enabled. [1] [2]
• Modified src/index.ts to retrieve the force input, pass it to deployment functions, and handle deployments with the force flag if specified. [1] [2] [3]

Test Coverage Improvements:

• Added a new test case in test/deploy.test.ts to validate that the --force flag is correctly included in deployment commands when enabled.
• Defined a forceDeploySingleSiteSuccess sample in test/samples/cliOutputs.ts to simulate successful deployments with the --force flag.

Documentation and Cleanup:

• Consolidated multi-line descriptions in action.yml into single-line format for better readability.

updated for Google CLA