fix: "dependency_version_2": true

[ocofaigh]

Description

Catalog team are recommending to set "dependency_version_2": true. The UI will handle the way it displays dependencies better when enabled

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.

[ocofaigh]

/run pipeline

[ocofaigh]

@surajsbharadwaj I'll let you handling merging, as I don't know if you wan't to generate a new release now or not

[ocofaigh]

@surajsbharadwaj maybe hold off on merge here - I found an issue. Will get back to you.

[surajsbharadwaj]

@ocofaigh do we have a reference to ibm_catatog.json file somewhere ? Like schema and stuff to know complete configuration support. ? Would be good to know

[ocofaigh]

Closing this for now - the catalog team need to provide migration support to move to this: https://github.ibm.com/ibmcloud/content-catalog/issues/5207