…i#347)

* [JENKINS-60738] Fix global configuration submission from UI

* [JENKINS-60738] Fix json binding for arrays

…jenkinsci#403)

- per `markdownlint`, use one bullet style and indentation consistently
  - previously used `-`, `*`, and `+`, should only use one (I chose `-`)
  - previously used both two space and four space indents for sub-bullets, should use one consistently (I chose two space)
  - same as my other PR, but this one is specific to one section and with almost no other grammatical or style changes

- colon (":") instead of comma (",") for each IDE

Several of the links were either redirecting, pointing to archived content, or pointing to no longer existing content

Specific changes:
- https://wiki.jenkins-ci.org URLs -> https://jenkins.io URLs
  - https://wiki.jenkins-ci.org/display/JENKINS/contributing was effectively 404'ing by redirecting to a Google search; https://www.jenkins.io/participate/ seems like the equivalent new URL
- https://issues.jenkins-ci.org/* -> https://issues.jenkins.io/*

…enkinsci#402)

grammar:
- "lot of people" -> "many people"
- unneeded "the" before "backward compatibility"
- "shall" -> "should"
- missing comma "," after various prepositions
- fix run-on sentence in `volatile` style
- etc

`markdownlint` issues:
- add syntax highlighting to Java codeblock example
- consistently use `-` instead of `*` or `+`
  - all three were used before, only one should be used consistently
- consistently use two space indentation for sub-bullets
  - sometimes it was two space, other times it was four space
- etc

* Migrate tests to JUnit5

* Migrate annotations and imports
* Migrate assertions
* Migrate GHMock Rule to Extension
* Migrate to DataProviderRunner to ParameterizedTest
* Remove public visibility for test classes and methods
* Minor clean up

* Migrate tests to JUnit Jupiter

* Migrate annotations and imports
* Migrate assertions
* Remove public visibility for test classes and methods
* Minor code cleanup
* Ban JUnit4 imports

---------

Co-authored-by: strangelookingnerd <[email protected]>

* Use `CredentialsProvider.findCredentialByIdInItemGroup`

* Dep released