Added CPO suggestion for plugin list & footnote with links to old documentation #PG-5194 & #PG-5185

[lachiebol]

Description

fetch-openapi-specs.php will now also fetch and store metadata about our plugins that we can use.

Should still work without new endpoint, as the plugin names still use the old endpoint, but descriptions wont be available.

Checklist

• [✔] I have understood, reviewed, and tested all AI outputs before use
• [✔] All AI instructions respect security, IP, and privacy rules

Review

• Functional review done
• Potential edge cases thought about (behaviour of the code with strange input, with strange internal state or possible interactions with other Matomo subsystems)
• Usability review done (is anything maybe unclear or think about anything that would cause people to reach out to support)
• Security review done
• Wording review done
• Code review done
• Tests were added if useful/possible
• Reviewed for breaking changes
• Developer changelog updated if needed
• New documentation added or existing documentation updated

[AltamashShaikh]

left 1 small fix comment and check this issue

app/templates/api-swagger-index.twig:13 always renders the colon separator even when pluginSpec.summary is empty. Since app/helpers/OpenApiSpecRegistry.php:148 intentionally returns no
  metadata when the JSON file is absent, the deployed page can show rows like Plugin Name: with no description. This is likely in the current branch unless the deploy process runs fetch-
  openapi-specs.php and publishes plugin_metadata_v1.0.0.json.