Correct Joomla release metadata before the first package

[Llewellynvdm]

The console update generator used a non-native information URL field and could reuse a version already recorded in its changelog. This fixes those metadata details before the first release.

• Emit Joomla infourl and an explicit site client for the console plugin.
• Reject reused changelog versions, misplaced pending markers and unprepared future update entries.
• Keep native git-user and OctoShoom action wiring unchanged. OctoJPack remains exclusively in the component workflow.
• Document the first rollout: release console and webservices through their manual workflows, then release the component package.
• Check out the standalone webservices repository in installed CI and pass it to the shared Joomla runner. The initial CI run exposed this missing test dependency after extraction; the corrected workflow tests exact webservices revision 94fd2a2b4ef802e1deef1050563cca2c0d879e1f.

Validation on 6e45707:

• PHP/source/native checks: https://github.com/joomengine/mcp_plugin/actions/runs/36453199181 — passed on PHP 8.3/8.4.
• Installed Joomla checks: https://github.com/joomengine/mcp_plugin/actions/runs/36453199175 — passed on PHP 8.3/8.4.
• Local checks: 18 metadata assertions, source completeness, PHP/workflow syntax and whitespace.
• The actual first-release metadata from all three repositories passes when prepared in temporary copies for example version 0.1.2.

Related PRs:

• Complete the webservices release trigger for the first package mcp_webservices#2
• Document the complete first-package rollout mcp_component#4

No release tags or package publication are performed by this PR.