docs: catalog prefix and permission changes for standard variation

[toddgiguere]

Description

Changes to some documentation in the stack standard variation in the catalog json file.

Release required?

• [ ] No release
• [ ] Patch release (x.x.X)
• [ ] Minor release (x.X.x)
• [ ] Major release (X.x.x)

Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

• [ ] If relevant, a test for the change is included or updated with this PR.
• [ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

• Use a conventional commit message to set the release level. Follow the guidelines.
• Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
• Use the Squash and merge option.

[toddgiguere]

/run pipeline

[toddgiguere]

/run pipeline

[toddgiguere]

/run pipeline

[terraform-ibm-modules-ops]

:tada: This PR is included in version 2.0.1 :tada:

The release is available on:

• GitHub release
• v2.0.1

Your semantic-release bot :package::rocket:

[terraform-ibm-modules-ops]

:tada: This PR is included in version 2.0.1 :tada:

The release is available on:

• GitHub release
• v2.0.1

Your semantic-release bot :package::rocket:

[terraform-ibm-modules-ops]

:tada: This PR is included in version 2.0.1 :tada:

The release is available on:

• GitHub release
• v2.0.1

Your semantic-release bot :package::rocket: