Update Docker tag in release workflow from 'latest' to 'dev' for non-…

[VadymFlamingo]

…workflow dispatch events

Summary by CodeRabbit

• Chores
  • Updated Docker image metadata tag configuration in release workflow.
  • Added automated upstream synchronization workflow to periodically merge upstream changes and create pull requests.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

This PR adds GitHub Actions workflow infrastructure changes: the release workflow now creates Docker images tagged with dev on the default branch and preserves those tags during registry cleanup; a new upstream sync workflow automates periodic synchronization of upstream develop branch changes with automatic PR creation.

Changes

Workflow Infrastructure

Layer / File(s)	Summary
Release workflow dev tag configuration .github/workflows/release.yml	Docker metadata now generates a dev tag enabled only on the default branch. GHCR cleanup rules are updated to exclude dev and test-.* tags from removal, preventing accidental deletion during registry maintenance.
Upstream sync automation workflow .github/workflows/sync-upstream.yml	New workflow runs weekly and on manual dispatch to sync upstream develop branch. It detects existing open sync PRs to prevent duplicates, verifies whether upstream changes are already merged, manages git operations and branch updates, and creates a new PR targeting develop when upstream changes are merged.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A rabbit built workflows with care,
Docker images tagged in the air,
Upstream syncs flow every week,
No merge conflicts here to seek,
Automation hops without a care! 🐰✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change in the PR—updating Docker tag configuration in the release workflow from 'latest' to 'dev' for non-default branches, which is the primary modification shown in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch hotfix/change_releases_flow

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}