feat: support include-ims-credentials annotation

[moritzraho]

Description

DRAFT
Depends on a release of adobe/aio-cli-plugin-app#899

Propose a new include-ims-credentials annotation at the action level. The annotation depends on a new IMS_OAUTH_S2S environment variable.

Here is an example:

runtimeManifest:
...
   myAction:
     annotations:
       include-ims-credentials: true 
       # note to reviewer, please let me know what you think of an `include-ims-credentials: ['oauth-s2s']` alternative

Rewrites to

runtimeManifest:
...
   myAction:
     inputs:
       __ims_oauth_s2s:
         client_id: abc
         client_secret: firstofthelist
         org_id: myOrg@AdobeOrg
         scopes: ["openid","AdobeID","abc"]
      __ims_env: stage

Note: the __ims prefix was chosen to align with __ow as in params.__ow_headers

Related Issue

Motivation and Context

How Has This Been Tested?

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!

[shazron]

include-ims-credentials: ['oauth-s2s'] are we planning on other credential support? if not, we can keep it simple with true

[purplecabbage]

Did you want to merge properties?
const env = Object.assign({}, DEFAULT_ENV, getCliEnv())

[purplecabbage]

small thing, I know this is a constant and typically we use SCREAMING_SNAKE, but the fact that it is declared like a local var means we can treat it differently. I think const ims_oauth_s2s_env_key would be clearer once we get to

 const imsAuthObject = {
    client_id: process.env[`${ims_oauth_s2s_env_key}_CLIENT_ID`]

and case is somewhat fluid when we get to getIncludeIMSCredentialsAnnotationInputs