feat: Add config-manager push variables

[dallinjsevy]

I added functions to ConfigManagerVariablesOps and CLI implementation for the config-manager push variables command.

I also added support for ESV placeholders in Config Manager, including global environment flags and updated conflicting flags.

This PR is dependent on the changes made to Frodo-lib in the feature/add-replaceEnvSpecifiValues PR.

[vscheuber]

@phalestrivir @dallinjsevy We have the same issue with the package version here, which I am getting to the bottom of. I believe it is caused by the new version-bump action I created to replace the marketplace one. I think I understand that part and will fix it.

However, when I run the test locally, I still get failures. Could you guys maybe run the tests with frodo-lib 4.4.0 and see if you get the same?

[phalestrivir]

@vscheuber @dallinjsevy I believe I fixed it (I pushed a fixup commit with the snapshot update I made). The tests are passing for me now locally.

[vscheuber]

@phalestrivir @dallinjsevy fantastic! I fixed the action to not base the new version on the source repo tags if the source repo is a fork but fallback to package.json. So that should fix the "there's a new version available" snapshot pollution. Tests are running now. If they all pass, I'll merge tonight and publish a new minor release.

[vscheuber]

@phalestrivir @dallinjsevy it looks like the same test suite is failing now in the pipeline as is failing for me when I run the tests locally:
FAIL test/e2e/idm-import.e2e.test.js

So the good news is the version issue is addressed but some tests are still failing.