Add CodeBoarding review and sync workflows

[ivanmilevtues]

Description

Adds CodeBoarding integration workflows for automated code review and context synchronization.

• codeboarding.yml: Triggers on PR open/reopen/ready_for_review and issue comments starting with /codeboarding. Runs CodeBoarding review on the PR.
• codeboarding-sync.yml: Runs on push to main and manual dispatch. Syncs CodeBoarding context via pull request strategy.

Fixes # (issue)

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No

[github-actions]

CodeBoarding review · failed

The review run could not generate a diagram. See workflow logs: https://github.com/CodeBoarding/aspire/actions/runs/31252577732

_{run 31252577732}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7a304d0405

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Pin the third-party action to a commit SHA

If this mutable upstream branch is force-pushed or the CodeBoarding repository is compromised, arbitrary replacement code will execute with this workflow's contents: write, pull-requests: write, and id-token: write permissions; the same mutable reference is also used by the review workflow with write permissions. Pin both action invocations to a reviewed full commit SHA so upstream branch changes cannot silently change the executed code.

Useful? React with 👍 / 👎.