* feat: add branch-based versioning for PR AMI buildsManually create unique Postgres version names in branch often leads toversion conflicts with the base branch versions. These conflicts forcedevelopers to deal with manual conflict resolution and unnecessaryrebuilds.To address this, this change implement automatic branch-based versioningfor AMI builds triggered via workflow_dispatch on non-develop andnon-release branches. The branch name is sanitized and appended to thePostgres version string.Example: Branch 'multi-version-ext/pg-partman' produces postgres version'multi-version-ext-pg-partman'* feat: add notice message for published AMI versionDisplay the published postgres AMI version using GitHub Actions `::notice` annotation.* feat: run actionlint on GitHub Actions workflowsStarting to lint GitHub Actions workflows with actionlint.* fix: generate a unique AMI versionGitHub run_id is appended to the version suffix to ensure uniqueness.It also enables to track the AMI back to the specific workflow run thatcreated it using url like:https://github.com/supabase/postgres/actions/runs/<run_id>

…d bin flake version workflowsOnce the AMI release workflow completes, it now triggers the pg_upgrade_scripts and pg_upgrade_bin flake version publishing workflows. This ensures that the necessary upgrade tools are published in sync with new PostgreSQL releases with the correct versioning.