chore: update existing_resource_group_name variable format and catalog entries

[piyush117]

Description

issue : https://github.ibm.com/GoldenEye/issues/issues/15895

Release required?

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

Release notes content

Start to consume catalog feature that supports picking default resource group. The catalog team have added logic to the resource group picker so that if user selects "Default" from the dropdown, even if it is not named "Default", the picker will pass the actual name of the default resource group in the account to Schematics.

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.

[piyush117]

/run pipeline

[piyush117]

/run pipeline

[piyush117]

/run pipeline

[terraform-ibm-modules-ops]

🎉 This PR is included in version 3.60.1 🎉

The release is available on:

• GitHub release
• v3.60.1

Your semantic-release bot 📦🚀