This is an autogenerated PR for updating HtmlUnit

It follows the migration guide

<details> <summary>Migration steps for cases the script can't handle</summary>

This migration currently can't handle HtmlOption changes properly. If it fails to compile on HtmlOption then revert the specific case:

--- a/src/test/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptorTest.java
+++ b/src/test/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptorTest.java
@@ -114,7 +114,7 @@ public class ExtendedEmailPublisherDescriptorTest {
      assertEquals(
              "Plain text should be selected by default",
              "text/plain",
-                contentType.getSelectedOptions().get(0).getValue());
+                contentType.getSelectedOptions().get(0).getValueAttribute());

</details>

Ping @timja if any questions

script source

Form entries in .repeated-chunk using .show-if-not-only CSS class are not hidden when they are alone, because there are missing CSS class definitions.

<!-- Comment: A great PR typically begins with the line below. Replace XXXXX with the numeric part of the issue ID you created in Jira. Note that if you want your changes backported into LTS, you need to create a Jira issue. See https://www.jenkins.io/download/lts/#backporting-process for more information. -->

See JENKINS-72018.

<!-- Comment: If the issue is not fully described in Jira, add more information here (justification, pull request links, etc.).

• We do not require Jira issues for minor improvements.
• Bug fixes should have a Jira issue to facilitate the backporting process.
• Major new features should have a Jira issue. -->

Testing done

Yes, and adding the missing CSS classes fix the issue.

<!-- Comment: Provide a clear description of how this change was tested. At minimum this should include proof that a computer has executed the changed lines. Ideally this should include an automated test or an explanation as to why this change has no tests. Note that automated test coverage is less than complete, so a successful PR build does not necessarily imply that a computer has executed the changed lines. If automated test coverage does not exist for the lines you are changing, you must describe the scenario(s) in which you manually tested the change. For frontend changes, include screenshots of the relevant page(s) before and after the change. For refactoring and code cleanup changes, exercise the code before and after the change and verify the behavior remains the same. -->

Proposed changelog entries

• Hide the delete button from the only repeatable element in configuration forms when at least one element is expected. (regression in 2.344)

<!-- Comment: The changelog entry should be in the imperative mood; e.g., write "do this"/"return that" rather than "does this"/"returns that". For examples, see: https://www.jenkins.io/changelog/ -->

Proposed upgrade guidelines

N/A

### Submitter checklist
- [X] The Jira issue, if it exists, is well-described.
- [X] The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see [examples](https://github.com/jenkins-infra/jenkins.io/blob/master/content/_data/changelogs/weekly.yml)). Fill in the **Proposed upgrade guidelines** section only if there are breaking changes or changes that may require extra steps from users during upgrade.
- [X] There is automated testing or an explanation as to why this change has no tests.
- [X] New public classes, fields, and methods are annotated with `@Restricted` or have `@since TODO` Javadocs, as appropriate.
- [X] New deprecations are annotated with `@Deprecated(since = "TODO")` or `@Deprecated(forRemoval = true, since = "TODO")`, if applicable.
- [X] New or substantially changed JavaScript is not defined inline and does not call `eval` to ease future introduction of Content Security Policy (CSP) directives (see [documentation](https://www.jenkins.io/doc/developer/security/csp/)).
- [X] For dependency updates, there are links to external changelogs and, if possible, full differentials.
- [X] For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@mention

<!-- Comment: If you need an accelerated review process by the community (e.g., for critical bugs), mention @jenkinsci/core-pr-reviewers. -->

Before the changes are marked as ready-for-merge:

### Maintainer checklist
- [ ] There are at least two (2) approvals for the pull request and no outstanding requests for change.
- [ ] Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
- [ ] Changelog entries in the pull request title and/or **Proposed changelog entries** are accurate, human-readable, and in the imperative mood.
- [ ] Proper changelog labels are set so that the changelog can be generated automatically.
- [ ] If the change needs additional upgrade steps from users, the `upgrade-guide-needed` label is set and there is a **Proposed upgrade guidelines** section in the pull request title (see [example](https://github.com/jenkinsci/jenkins/pull/4387)).
- [ ] If it would make sense to backport the change to LTS, a Jira issue must exist, be a _Bug_ or _Improvement_, and be labeled as `lts-candidate` to be considered (see [query](https://issues.jenkins.io/issues/?filter=12146)).

<a href="https://gitpod.io/#https://github.com/jenkinsci/jenkins/pull/8491"><img src="https://gitpod.io/button/open-in-gitpod.svg"/></a>

Testing done

Proposed upgrade guidelines

N/A

### Submitter checklist
- [ ] The Jira issue, if it exists, is well-described.
- [ ] The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see [examples](https://github.com/jenkins-infra/jenkins.io/blob/master/content/_data/changelogs/weekly.yml)). Fill in the **Proposed upgrade guidelines** section only if there are breaking changes or changes that may require extra steps from users during upgrade.
- [ ] There is automated testing or an explanation as to why this change has no tests.
- [ ] New public classes, fields, and methods are annotated with `@Restricted` or have `@since TODO` Javadocs, as appropriate.
- [ ] New deprecations are annotated with `@Deprecated(since = "TODO")` or `@Deprecated(forRemoval = true, since = "TODO")`, if applicable.
- [ ] New or substantially changed JavaScript is not defined inline and does not call `eval` to ease future introduction of Content Security Policy (CSP) directives (see [documentation](https://www.jenkins.io/doc/developer/security/csp/)).
- [ ] For dependency updates, there are links to external changelogs and, if possible, full differentials.
- [ ] For new APIs and extension points, there is a link to at least one consumer.

Before the changes are marked as ready-for-merge:

### Maintainer checklist
- [ ] There are at least two (2) approvals for the pull request and no outstanding requests for change.
- [ ] Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
- [ ] Changelog entries in the pull request title and/or **Proposed changelog entries** are accurate, human-readable, and in the imperative mood.
- [ ] Proper changelog labels are set so that the changelog can be generated automatically.
- [ ] If the change needs additional upgrade steps from users, the `upgrade-guide-needed` label is set and there is a **Proposed upgrade guidelines** section in the pull request title (see [example](https://github.com/jenkinsci/jenkins/pull/4387)).
- [ ] If it would make sense to backport the change to LTS, a Jira issue must exist, be a _Bug_ or _Improvement_, and be labeled as `lts-candidate` to be considered (see [query](https://issues.jenkins.io/issues/?filter=12146)).

<a href="https://gitpod.io/#https://github.com/jenkinsci/jenkins/pull/8519"><img src="https://gitpod.io/button/open-in-gitpod.svg"/></a>

While compiling with -Dmaven.compiler.release=21 I got the following compilation failure:

Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.11.0:compile (default-compile) on project jenkins-core: Compilation failure
/home/basil/src/jenkinsci/jenkins/core/src/main/java/hudson/tasks/Publisher.java:[135,24] error: types Comparator<T> and List<E> are incompatible;
  class DescriptorExtensionListImpl inherits unrelated defaults for reversed() from types Comparator and List
  where T,E are type-variables:
    T extends Object declared in interface Comparator
    E extends Object declared in interface List

This is because of the addition of incompatible reversed() methods between these two interfaces. Thinking about this more closely, it makes little sense for anything to implement both List and Comparator so I split out the comparator into its own class to solve the conflict.

Testing done

mvn clean verify -DskipTests -Dmaven.compiler.release=21 -Dmaven.compiler.testRelease=21 failed before this PR and passed after it.

Proposed changelog entries

N/A

Proposed upgrade guidelines

N/A

### Submitter checklist
- [ ] The Jira issue, if it exists, is well-described.
- [ ] The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see [examples](https://github.com/jenkins-infra/jenkins.io/blob/master/content/_data/changelogs/weekly.yml)). Fill in the **Proposed upgrade guidelines** section only if there are breaking changes or changes that may require extra steps from users during upgrade.
- [ ] There is automated testing or an explanation as to why this change has no tests.
- [ ] New public classes, fields, and methods are annotated with `@Restricted` or have `@since TODO` Javadocs, as appropriate.
- [ ] New deprecations are annotated with `@Deprecated(since = "TODO")` or `@Deprecated(forRemoval = true, since = "TODO")`, if applicable.
- [ ] New or substantially changed JavaScript is not defined inline and does not call `eval` to ease future introduction of Content Security Policy (CSP) directives (see [documentation](https://www.jenkins.io/doc/developer/security/csp/)).
- [ ] For dependency updates, there are links to external changelogs and, if possible, full differentials.
- [ ] For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@mention

<!-- Comment: If you need an accelerated review process by the community (e.g., for critical bugs), mention @jenkinsci/core-pr-reviewers. -->

Before the changes are marked as ready-for-merge:

### Maintainer checklist
- [ ] There are at least two (2) approvals for the pull request and no outstanding requests for change.
- [ ] Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
- [ ] Changelog entries in the pull request title and/or **Proposed changelog entries** are accurate, human-readable, and in the imperative mood.
- [ ] Proper changelog labels are set so that the changelog can be generated automatically.
- [ ] If the change needs additional upgrade steps from users, the `upgrade-guide-needed` label is set and there is a **Proposed upgrade guidelines** section in the pull request title (see [example](https://github.com/jenkinsci/jenkins/pull/4387)).
- [ ] If it would make sense to backport the change to LTS, a Jira issue must exist, be a _Bug_ or _Improvement_, and be labeled as `lts-candidate` to be considered (see [query](https://issues.jenkins.io/issues/?filter=12146)).

<a href="https://gitpod.io/#https://github.com/jenkinsci/jenkins/pull/8520"><img src="https://gitpod.io/button/open-in-gitpod.svg"/></a>

Bumps stapler.version from 1802.1804.va_8d30483a_7f7 to 1814.vdc9dd5217ee2. Updates org.kohsuke.stapler:stapler from 1802.1804.va_8d30483a_7f7 to 1814.vdc9dd5217ee2 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jenkinsci/stapler/releases">org.kohsuke.stapler:stapler's releases</a>.</em></p> <blockquote> <h2>1814.vdc9dd5217ee2</h2> <h2>👷 Changes for plugin developers</h2> <ul> <li>Bump jetty.version from 10.0.15 to 10.0.16 (<a href="https://redirect.github.com/jenkinsci/stapler/issues/489">#489</a>) <a href="https://github.com/dependabot"><code>@​dependabot</code></a></li> </ul> <h2>👻 Maintenance</h2> <ul> <li>Simplify test matrix (<a href="https://redirect.github.com/jenkinsci/stapler/issues/486">#486</a>) <a href="https://github.com/MarkEWaite"><code>@​MarkEWaite</code></a></li> <li>Test on Java 21 (<a href="https://redirect.github.com/jenkinsci/stapler/issues/485">#485</a>) <a href="https://github.com/MarkEWaite"><code>@​MarkEWaite</code></a></li> </ul> <h2>📦 Dependency updates</h2> <ul> <li>Bump jenkins from 1.102 to 1.105 (<a href="https://redirect.github.com/jenkinsci/stapler/issues/479">#479</a>, <a href="https://redirect.github.com/jenkinsci/stapler/issues/484">#484</a>, <a href="https://redirect.github.com/jenkinsci/stapler/issues/488">#488</a>) <a href="https://github.com/dependabot"><code>@​dependabot</code></a></li> <li>Bump jenkins-test-harness-htmlunit (<a href="https://redirect.github.com/jenkinsci/stapler/issues/481">#481</a>, <a href="https://redirect.github.com/jenkinsci/stapler/issues/487">#487</a>) <a href="https://github.com/dependabot"><code>@​dependabot</code></a></li> <li>Bump jelly.version from 1.1-jenkins-20230124 to 1.1-jenkins-20230713 (<a href="https://redirect.github.com/jenkinsci/stapler/issues/480">#480</a>) <a href="https://github.com/dependabot"><code>@​dependabot</code></a></li> <li>Bump jellydoc-maven-plugin.version (<a href="https://redirect.github.com/jenkinsci/stapler/issues/477">#477</a>, <a href="https://redirect.github.com/jenkinsci/stapler/issues/478">#478</a>) <a href="https://github.com/dependabot"><code>@​dependabot</code></a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/jenkinsci/stapler/commits">compare view</a></li> </ul> </details> <br />

Updates org.kohsuke.stapler:stapler-groovy from 1802.1804.va_8d30483a_7f7 to 1814.vdc9dd5217ee2 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jenkinsci/stapler/releases">org.kohsuke.stapler:stapler-groovy's releases</a>.</em></p> <blockquote> <h2>1814.vdc9dd5217ee2</h2> <h2>👷 Changes for plugin developers</h2> <ul> <li>Bump jetty.version from 10.0.15 to 10.0.16 (<a href="https://redirect.github.com/jenkinsci/stapler/issues/489">#489</a>) <a href="https://github.com/dependabot"><code>@​dependabot</code></a></li> </ul> <h2>👻 Maintenance</h2> <ul> <li>Simplify test matrix (<a href="https://redirect.github.com/jenkinsci/stapler/issues/486">#486</a>) <a href="https://github.com/MarkEWaite"><code>@​MarkEWaite</code></a></li> <li>Test on Java 21 (<a href="https://redirect.github.com/jenkinsci/stapler/issues/485">#485</a>) <a href="https://github.com/MarkEWaite"><code>@​MarkEWaite</code></a></li> </ul> <h2>📦 Dependency updates</h2> <ul> <li>Bump jenkins from 1.102 to 1.105 (<a href="https://redirect.github.com/jenkinsci/stapler/issues/479">#479</a>, <a href="https://redirect.github.com/jenkinsci/stapler/issues/484">#484</a>, <a href="https://redirect.github.com/jenkinsci/stapler/issues/488">#488</a>) <a href="https://github.com/dependabot"><code>@​dependabot</code></a></li> <li>Bump jenkins-test-harness-htmlunit (<a href="https://redirect.github.com/jenkinsci/stapler/issues/481">#481</a>, <a href="https://redirect.github.com/jenkinsci/stapler/issues/487">#487</a>) <a href="https://github.com/dependabot"><code>@​dependabot</code></a></li> <li>Bump jelly.version from 1.1-jenkins-20230124 to 1.1-jenkins-20230713 (<a href="https://redirect.github.com/jenkinsci/stapler/issues/480">#480</a>) <a href="https://github.com/dependabot"><code>@​dependabot</code></a></li> <li>Bump jellydoc-maven-plugin.version (<a href="https://redirect.github.com/jenkinsci/stapler/issues/477">#477</a>, <a href="https://redirect.github.com/jenkinsci/stapler/issues/478">#478</a>) <a href="https://github.com/dependabot"><code>@​dependabot</code></a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/jenkinsci/stapler/commits">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

Request @NotMyFault @Vlatombe @MarkEWaite to close the PR

Describe the bug Executing tests on systems, where master isn't set es default git branch fails. The tests are going to use the configured branch name instead, thus failing on everything based on master assumptions.

Since the setup is done by calling init() of GitSampleRepoRule (git plugin), it's better fixed there (--> I'm going to submit a PR).

To Reproduce Steps to reproduce the behavior:

1. Set another branch, eg. main, as default branch globally
2. Run tests
3. Some tests fail due to missing master

Expected behavior Tests should pass and not depend on machine settings.

Screenshots N/A

Desktop (please complete the following information): N/A

Smartphone (please complete the following information): N/A

Additional context This issue is used for documentation, as others may run into the problem too.

Update to 2.346.3 LTS version and update BOM / POM to their latest versions. Some dependencies require at least .3.

The update includes a fix for #111.

closes #111

<!-- Please describe your pull request here. -->

• [x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• [x] Ensure that the pull request title represents the desired changelog entry
• [x] Please describe what you did
• [x] Link to relevant issues in GitHub or Jira
• [x] Link to relevant pull requests, esp. upstream and downstream changes
• [x] Ensure you have provided tests - that demonstrates feature works or fixes the issue

<!-- Put an x into the [ ] to show you have filled the information. The template comes from https://github.com/jenkinsci/.github/blob/master/.github/pull_request_template.md You can override it by creating .github/pull_request_template.md in your own repository -->