fix: bump kms and vpc modules

[shemau]

Description

Manually bump modules used is tests. The VPC upgrade will introduce a resource name change, which can be safely ignored, since it used only for testing (and not in the main module itself).

Only the tests are changing, so no need to create a release.

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.

[shemau]

/run pipeline

[shemau]

The following error is detected during upgrade:

         	Messages:   	Resource(s) identified to be updated 
        	            	Name: vpc
        	            	Address: module.vpc.ibm_is_vpc.vpc[0]
        	            	Actions: [update]
        	            	DIFF:
        	            	  Before: 
        	            		{"name":"mysql-upg-8oze5q-vpc-vpc"}
        	            	  After: 
        	            		{"name":"mysql-upg-8oze5q-vpc"}

Since this is in a test and unrelated to this module and was the only error reported, the upgrade tests can be skipped.

[shemau]

/run pipeline

[ocofaigh]

/run pipeline

[shemau]

/run pipeline

[terraform-ibm-modules-ops]

🎉 This PR is included in version 1.9.1 🎉

The release is available on:

• GitHub release
• v1.9.1

Your semantic-release bot 📦🚀