feat(breaking): standardize ims credential env vars, make them predictable and easy to add to actions

[MichaelGoberling]

Description

Breaking change

Proposing to make it so ims credential env vars are easy to pass to actions.

Today, when we aio app use or app init, we get something like this in .env:

AIO_ims_contexts_aio-4566206088345584002_client__id=abcd1245...

This PR proposes standardizing these properties to something easier to predict, the solution is to prefix each field in the credential with IMS_:

IMS_CLIENT_ID=abcd12345...
IMS_ORG_ID=123@AdobeOrg
...

And then they can be passed to Runtime actions:

          inputs:
            IMS_CLIENT_ID: $IMS_CLIENT_ID

For projects with multiple credentials, the env vars are postfixed with _{index}:

IMS_CLIENT_ID_2=abcd12345...

Related Issue

N/A

Motivation and Context

Make it easier to use IMS credential env vars

How Has This Been Tested?

• npm run test
• Locally linked plugin, aio app use and aio app init

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!