Always update artifacts_present variable in artifact publish (#414)

DownloadCargoBinaryFromGitHub: Find most recent release with assets (#…

…410)

Currently, the `cargo-binstall` most recent release in the binstall repo
does not actually have the binstall binary. This change allows the
search to find the most recent release that has the expected binaries to
handle the case when other releases might also be in release list that
do not have the expected binaries.

Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>

Version.njk: Update to Ubuntu 24.04 container (#406)

Update pipelines and devcontainer files to use the 24.04 container. Also
updates Mu DevOps version for the upcoming release.

Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>

.sync/Version.njk: Update cargo-make and cargo-tarpaulin to latest (#397

)

Since `cargo-binstall` is being used to install Rust binaries, update to
the latest version of `cargo-make` and `cargo-tarpaulin`.

Note: `RustSetupSteps.yml` in this repo gets updated from this version
during the file sync.

Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>

Add artifacts_binary and artifacts_other parameters to Jobs/PrGate.yml (

#392)

Add artifacts_binary and artifacts_other parameters to Jobs/PrGate.yml
to let consumer able to customize the binary and other path for
publishing content to pipeline artifact

Co-authored-by: Aaron <aaronpop@microsoft.com>

Update Release Drafter for Dev Branches (#387)

Changes the way release drafter handles drafting releases on repos with
release branches (which have dev branches now).

Ultimately, a release is drafted for the dev branch and the release
branch. The releases are differentiated by both their release title and
tag.

- Release Branch
  - Title: `release-v<version>`
  - Tag: `v<version>`
- Dev Branch
  - Title: `dev-v<version>`
  - Tag: `dev-v<version>`

Note that the tag for the release branch follows the same convention as
existing release tags.

The "release branch" release includes all pull requests made to the dev
branch with the `type:backport` label since the last "dev branch"
release. For this reason, the "dev branch" and "release branch" should
be released at the same time. Then, this effectively results in the
"release branch" having all relevant changes since the last release. The
"dev branch" release will be based at the same point in history as the
"release branch" release but include all changes not just those with the
`type:backport` label.

The "release branch" release for the current release branch should be
marked as "latest". For example, if "release/202311" and
"release/202405" exist, the "release/202405" "release branch" release
would be marked as latest.

The `release-drafter/release-drafter` action is still used.

Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>

Add release branch backport workflow (#386)

Closes #372 

This new workflow will attempt to automatically cherry-pick marked
contributions to a development branch to its corresponding release
branch. If a merge conflict occurs, the commit is committed to a new
branch with merge markers and then a PR is created into the target
branch with those markers. The PR is labeled with
`type:release-merge-conflict` to indicate that it needs manual
resolution.

The PR (if created) is expected to fail compilation and status checks of
course due to the merge conflict markers. A human should then checkout
the PR branch, resolve the conflicts, and push the changes back to the
PR branch.

---

- To mark a PR going into the development branch so that it should be
cherry-picked to the release branch, add the `type:backport` label to
the PR.

---

Notes:

- The workflow is synced to all repos that currently have a `dev`
branch.
- Each repo that `backport-to-release-branch.yml` is synced to must have
a `CHERRY_PICK_TOKEN` defined with repo write permission.

Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>

.sync/Version.njk: Update to Mu DevOps v12.2.0

See the following comparison for details of the changes
between these releases:

v12.0.2...v12.2.0

Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>

PrGate.yml: Add extra_pre_build_steps param (#378)

Adds a new template parameter called `extra_pre_build_steps` that allows
a step list to run before any stuart build related commands are
executed.

Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>

Version.njk: Update to container version d1e4ff1 (#374)

Main reason to update is to use the latest Rust versions
in Version.njk.

A complete list of changes compared to the previous container
version (`0e124c1`) is in:

0e124c1...d1e4ff1.

Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>