adding latest CVT version

[shivaprasad-metimath]

Summary and Scope

Summarize what has changed. Explain why this PR is necessary. What is impacted? Is this a new feature, critical bug fix, etc?

Bug fixes to CDS have been included in CVT pkg, hence need to include the latest version
cvt-1.5.2-20230704071632_a2da8d744eec.x86_64.rpm

Is this change backwards incompatible, backwards compatible, or a backwards compatible bugfix?

Issues and Related PRs

https://jira-pro.it.hpe.com:8443/browse/CASMCVT-229

List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.

• Resolves [issue id](issue link)
• Change will also be needed in <insert branch name here>
• Future work required by [issue id](issue link)
• Documentation changes required in [issue id](issue link)
• Merge with/before/after <insert PR URL here>

Testing

List the environments in which these changes were tested.
brook and starlord the fixes have been tested

Tested on:

• <development system>
• Local development environment
• Virtual Shasta

Test description:

How were the changes tested and success verified? If schema changes were part of this change, how were those handled in your upgrade/downgrade testing?

• Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)?
• Were continuous integration tests run? If not, why?
• Was upgrade tested? If not, why?
• Was downgrade tested? If not, why?
• Were new tests (or test issues/Jiras) created for this change?

Risks and Mitigations

Are there known issues with these changes? Any other special considerations?

Pull Request Checklist

• Version number(s) incremented, if applicable
• Copyrights updated
• License file intact
• Target branch correct
• CHANGELOG.md updated
• Testing is appropriate and complete, if applicable
• HPC Product Announcement prepared, if applicable

[denniswalker]

/backport stable/1.5

[github-actions]

Backporting into branch stable/1.5 was successful. New PR: #2562