[FIXED JENKINS-29798] Failed to listen to incoming slave connection

Update javadoc-plugin version

typofix - https://github.com/vlajos/misspell_fixer

Noting JENKINS-29936

Improved unit test for Util.deleteFile & Util.deleteRecursive

Added unit test for Util.deleteRecursive(File)

[JENKINS-28440] Reject configurations with errors in critical fields via REST / CLI

[JENKINS-29936] when removing an item use ACL.SYSTEM.

The OldDataMonitor should be using ACL.system not the ACL of the calling
thread - this also avoids the deadlock when an authorization strategy is
being saved (locking the auth strategy) which will call into the ODM at
the same point the ODM is being called an a Run has been saved (which will
cause a lookup of the job which will do a permissions check).

Fixed typos in pt_BR and pt_PT translations

[FIXED JENKINS-2327] Do not display 'No changes' if changelog calcula…

[JENKINS-28690] Aha! So I believe this will fully resolve any of these kinds of deadlocks

[FIXES PR#1777] Make accessing pendingLaunches lock free

Update link to Groovy

Codehaus terminated all services - now Groovy's new home is groovy-lang.org.

- My objection to #1777 is that it is introducing more locking. The ultimate aim is to make
  node provisioning and queue maintenance completely lock free. Thus adding more locks than
  is strictly required is a bad plan.
- We cannot completely remove provisioningLock at this time as it is used to ensure that
  only one provisioning activity can take place for a given label at a time.
- This change ensures that the provisioningLock is only used by the NodeProvisioner for
  its internal thread guarantees and is thus no-longer used accidentally by any
  external threads

- Without this, then it becomes a question of find catch and release for each potential code path that
  might end up restoring the interrupt flag on the current thread.
- Since standard Lock support is kind enough to restore the interrupt flag on the current thread
  when blocked waiting for the lock, that would be a hiding to nothing
- I welcome others to review my logic detailed in the code comment
- I am leaving the code comment as this is IMHO too important to assume that somebody will
  check the git commit history

Factor tcpSlaveAgentListener logic to a single method able to shutdown
existing listener if required, then launch a new one if it needs to.

Also, the administrative monitor gets cleared if we had previously a
taken port and changed to a valid port.

few chances there’s another implementation
but if one exists Function.isWindows would probably be wrong implementation

Avoid "EmptyStackException: null" in Items#getCanonicalName