Create workflow to auto-update MPC user docs

[enkeefe00]

Add a GitHub workflow to create/update an MR for updating the MPC user doc's Available Platform Variants by Cluster table whenever changes to a cluster's MPC host config are detected in a PR.

Assisted by: Cursor & Gemini

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: enkeefe00
Once this PR has been reviewed and has the lgtm label, please assign adambkaplan for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

🤖 Gemini AI Assistant Available

Hi @enkeefe00! I'm here to help with your pull request. You can interact with me using the following commands:

Available Commands

• @gemini-cli /review - Request a comprehensive code review

  • Example: @gemini-cli /review Please focus on security and performance

• @gemini-cli <your question> - Ask me anything about the codebase

  • Example: @gemini-cli How can I improve this function?
  • Example: @gemini-cli What are the best practices for error handling here?

How to Use

1. Simply type one of the commands above in a comment on this PR
2. I'll analyze your code and provide detailed feedback
3. You can track my progress in the workflow logs

Permissions

Only OWNER, MEMBER, or COLLABORATOR users can trigger my responses. This ensures secure and appropriate usage.

---

This message was automatically added to help you get started with the Gemini AI assistant. Feel free to delete this comment if you don't need assistance.

[github-actions]

🤖 Hi @enkeefe00, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[enkeefe00]

@gemini-cli /review

[sadlerap]

Some thoughts, largely looks good to me.

[sadlerap]

What do you think on triggering this workflow on pushes instead of on pull requests? I'm worried about the following sequence of events:

1. we open a PR to infra-deployments
2. this workflow opens a MR on gitlab
3. we merge that MR
4. we later decide that the PR is wrong and close it.

This puts our documentation on gitlab out-of-sync with what we have on github and requires manual intervention to cleanup (sure, it's as easy as git revert, but that's a manual step I'd like to remove from ever happening in the first place).

I'm fine with this PR either way, just food for thought.

[sadlerap]

Since we set the path on the trigger for this PR, this check is redundant.

Suggested change

	if [ -z "$CHANGED_FILES" ]; then
	echo "No MPC host-values.yaml files were changed in this PR"
	echo "has_host_values=false" >> $GITHUB_OUTPUT
	exit 0
	fi