Previously, we uploaded SARIF artifacts in the `analyze-post` step and database and log artifacts in the `init-post` step. As we migrate to the updated `artifact` dependencies, we want to switch to uploading all artifacts in one step.

In order to upload all artifacts in one go and maintain the artifacts at the root of the debug directory, we first move SARIF artifacts to the database directory. This should not affect any other consumers of the SARIF file as this occurs in the `init-post` step.

Previously, we uploaded combined SARIF artifacts in both the `analyze-post` and `upload-sarif-post` steps. This change ensures that these artifacts are uploaded at most once — in `analyze-post` if it is a first-party run and `upload-sarif-post` if it is a third-party run.

This is a defensive check because as we upgrade to the new `artifact` dependencies we will not be able to upload artifacts to the same artifact directory.

More accurately describes what these artifacts are, rather than the step they're uploaded in.

Mergeback v3.26.7 refs/heads/releases/v3 into main

Co-authored-by: Andrew Eisenberg <aeisenberg@github.com>

Fix incorrect documentation about the `token` input to the Actions.

The script `.github/update-release-branch.py` uses the `git` command
to push changes. Therefore we need to ensure that `git` authenticates
with a token that has the `workflows` write permision.

This change restore the GitHub token used by the script to access the
API and applies the `workflows` write permission to the token used by `git`.

…cts-upload

Refactor: prepare debug artifacts for `artifact` upgrades

…-for-auth

Use generated token on checkout

…ct-robustness

Improve the robustness of creating and uploading debug artifacts

…er-logging

Improve logging when preparing and uploading debug artifacts

…nings

Turn URI errors into warnings

Update default bundle to 2.19.0

Merge main into releases/v3

GITHUB_TOKEN is no longer defined; we should use either the workflow token or the app one. Here we try using the app one.

…n-to-backport

Backport workflow: try using the app token

This reverts commit 81dc191.

This reverts commit 8c041af.

….8-574aaa581