feat: use existing scc instance

[kierramarie]

Description

Updated version locator to newest version of SCC and included variable for existing SCC instance.

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.

[kierramarie]

/run pipeline

[kierramarie]

Test failed because of projects limit, but the SCC part of the project was successfully deployed.

[kierramarie]

/run pipeline

[ocofaigh]

@kierramarie what happened to to this one?

[kierramarie]

/run pipeline

[ocofaigh]

@kierramarie editing the comment wont trigger pipeline. Needs a new comment. I'll leave one now to trigger..

[ocofaigh]

Oh but first it seems as if your missing the new variable in the ibm_catalog.json

[kierramarie]

/run pipeline

[ocofaigh]

Can we update the existing resources test to test existing SCC so we test the feature in the stack?

PS: Projects seems a little unstable at the moment so I suspect thats why tests are failing. Lets see what tests look like after your next commit

[kierramarie]

/run pipeline

[kierramarie]

blocked by terraform-ibm-modules/terraform-ibm-scc-da#242