chore: add the scripts back due to a bug in projects

[Aashiq-J]

Description

There is an ongoing bug in the projects which picks runs the migration script even if we removed it in the newer version which is causing an error. So, for now adding the script back till the issue is fixed.

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.

[Aashiq-J]

/run pipeline

[ocofaigh]

I'll hold off on this - I would prefer get the fix from Project first. But use this as backup if we need to force a new release before then

[ocofaigh]

@Aashiq-J We don't have to add the exact migration script back in. As a workaround we can just have a script that does nothing. Want to update this?

[ocofaigh]

Oh and @Aashiq-J When updating, we will need to change back the catalog pipeline validation to use projects again. Can you also make that change please (for reference see #948)

[ocofaigh]

/run pipeline

[terraform-ibm-modules-ops]

🎉 This PR is included in version 7.2.0 🎉

The release is available on:

• GitHub release
• v7.2.0

Your semantic-release bot 📦🚀