Add environment value and set config appropriately

[ri-roee]

Description of the change

By default the app-config.production.yaml file is not used in bootup process of backstage. This leads to misconfiguration and confusion (see attached issue). This PR is a no-op for folks who continue to not set backstage.environment value, however those using the production string will have the config correctly passed in.

Existing or Associated Issue(s)

https://github.com/backstage/backstage/issues/25189

Additional Information

It is not strictly required to pass in --config app-config.yaml however I felt that being extra verbose would be clearer in this case.

I noticed that the ct install tests were failing, even off master, and I believe this is due to the NODE_ENV not being set correctly thus causing the guest auth provider to error out. I now set that env var based on the backstage environment

Checklist

• [x] Chart version bumped in Chart.yaml according to semver.
• [x] Variables are documented in the values.yaml and added to the README.md. The helm-docs utility can be used to generate the necessary content. Use helm-docs --dry-run to preview the content.
• [x] JSON Schema generated.
• [x] List tests pass for Chart using the Chart Testing tool and the ct lint command.

[github-actions[bot]]

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

[ri-roee]

@ChrisJBurns sorry to tag you in this directly, but wanted to make sure you saw it as its marked stale! Would appreciate a review :)

[github-actions[bot]]

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!