feat: Install the components after merge to Observe (WEKAPP-605465)

[mvoloshin0458]

With this CI, the components will be install Observe PRs. It looks at the ticket(s) and installs only to matched PRs

[mvoloshin0458]

@sofa-tata, we need to use a token to push to PRs in gohome. How is it done with a token for the NPM? Who updates it? I guess the same should be done with this token

[cursor]

PR Summary

Medium Risk
Medium risk because this introduces an automated workflow that checks out and pushes commits to external PR branches based on ticket-matching heuristics and a privileged token, so mis-matches or auth issues could cause unintended updates.

Overview
Adds a new GitHub Actions workflow (update-observe-frontend.yml) that triggers on release publication, extracts the released version and ticket IDs from the tagged commit message, and searches open weka/gohome PRs whose title/body/branch contains those tickets.

For each matched PR, the workflow checks out the PR branch, runs yarn add "@weka/weka-ui-components@^<version>" in observe/frontend, and commits + pushes the updated package.json/yarn.lock back to the branch.

^{Written by Cursor Bugbot for commit 11cc6c9. This will update automatically on new commits. Configure here.}