[dotnet][java][js][py][rb][rust] Update firefox_standalone Docker digest to 1333df1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
firefox_standalone	oci_pull	digest	b6d8279 -> 1333df1

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[qodo-merge-pro]

CI Failure Feedback 🧐

(Checks updated until commit e8134d0)

Action: Rust / Build / Build

Failed stage: Pull latest changes [❌]

Failed test name: ""

Failure summary: The action failed because Git encountered a merge conflict and couldn't automatically determine how to reconcile divergent branches. This typically happens when: There are conflicting changes between the local and remote branches Git's pull strategy is not configured The repository needs explicit instructions on how to handle branch divergence

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 164: hint: git config pull.rebase true # rebase 165: hint: git config pull.ff only # fast-forward only 166: hint: 167: hint: You can replace "git config" with "git config --global" to set a default 168: hint: preference for all repositories. You can also pass --rebase, --no-rebase, 169: hint: or --ff-only on the command line to override the configured default per 170: hint: invocation. 171: fatal: Need to specify how to reconcile divergent branches. 172: ##[error]Process completed with exit code 128.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.