feat: update names of the stacks

[jor2]

Description

update member names https://github.com/terraform-ibm-modules/stack-ibm-core-security-services/issues/34 https://github.com/terraform-ibm-modules/stack-ibm-core-security-services/issues/40

Release required?

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

Release notes content

Update member names

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.

[jor2]

/run pipeline

[jor2]

/run pipeline

[jor2]

/run pipeline

[jor2]

/run pipeline

[jor2]

/run pipeline

[jor2]

/run pipeline

[jor2]

/run pipeline

[ocofaigh]

@jor2 same issue in tests, however it must be something specific to your change because tests are working in https://github.com/terraform-ibm-modules/stack-ibm-core-security-services/pull/41

[jor2]

/run pipeline

[jor2]

/run pipeline

[jor2]

/run pipeline

[jor2]

/run pipeline