Replace legacy CC API integration (api.creativecommons.org) #9397

Is your feature request related to a problem? Please describe.
The legacy CC API (api.creativecommons.org) is on borrowed time.

Describe the solution you'd like
We (Creative Commons Technology team members) would like to collaborate with DSpace developers to develop a solution that meets or exceeds the current solution. I expect a few YAML or JSON files would be easier to work with and provide a better end-user experience.

It looks like dspace-api/src/main/java/org/dspace/license/CCLicenseConnectorServiceImpl.java is where the legacy CC API integration lives.

Additional context

• Current CC legal tools (licenses + CC0 public domain dedication) are a much smaller solution space than they were under 3.0 of the licenses
  • With version 4, there are 6 licenses (all international)
  • With version 3, there are 264 licenses (6 each of unported and ported/jurisdiction specific)
• The CC legal tools have never changed very rapidly--the legacy CC API returns the same information now as it did when it received its last substantial update, 11 years ago.
• cc-archive/cc.api: Legacy API to integrate the Creative Commons licensing engine into third party applications
• The legacy ccEngine was replaced by the new CC Legal Tools on 2023-09-27
  • new CC Legal Tools
    • creativecommons/cc-legal-tools-app: Legal tool (licenses, public domain dedication, etc.) management application for Creative Commons
    • creativecommons/cc-legal-tools-data: Legal tool (licenses, public domain dedication, etc.) data for Creative Commons
  • see the ccEngine section of the cc-archive/cc.engine repository's README.md for the list of legacy ccEngine repositories