fix: main branch failure during PR tests

[shemau]

Description

Fixes for recent test failure during renovate PR pipelines

1. Upgrade test name too long
2. Security enforced test does not take flags to enable to security
3. Upgrade test is private, so it has to be run in schematics

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

[rajatagarwal-ibm]

@shemau just like normal tests for Security Enforced, would you like to run upgraded tests on Schematics as well?

[shemau]

/run pipeline

[shemau]

common-dev-assets and go updates required to include schematics upgrade test functions

[shemau]

/run pipeline

[shemau]

/run pipeline

[whoffler]

ok code engine only deployed in security enforced and fully configurable... and enable_kibana_dashboard needs to be enabled to run into this issue. LGTM

[terraform-ibm-modules-ops]

🎉 This PR is included in version 2.0.1 🎉

The release is available on:

• GitHub release
• v2.0.1

Your semantic-release bot 📦🚀