* [JENKINS-39465] - Tweak processing of enabled and disabled protocols in Jenkins instance

Due to whatever reason, without a definition of an array recipient field the data goes to the disk in the following way:

```
<enabledAgentProtocol>JNLP3-connect</enabledAgentProtocol>
<enabledAgentProtocol>JNLP4-connect</enabledAgentProtocol>
```

It is supposed to processed by Implicit array correctly, but it does not actually happen.
With a fix the data is being stored in another format:

```
  <enabledAgentProtocols>
    <string>JNLP3-connect</string>
    <string>JNLP4-connect</string>
  </enabledAgentProtocols>
```

This data now works correctly and gets deserialized correctly. readResolve() just adds a fallback for the case when Implicit array handling starts behaving correctly (?).

* [JENKINS-39465] - Add configuration roundtrip tests

* [JENKINS-39465] - Jenkins#agentProtocols cache must be invalidated when we reload the configuration

* [JENKINS-39465] - Remove obsolete comment from Tests

* Coarse fix for JENKINS-39555 - don't do the actions initialization by helper method

* Small cleanup of docs, import

* Testcase

* Review changes

* Changelog: Add the 2.29 release notice

* Fix the link

* Add some tests to  current behaviour of getLog method

* getLog(maxLines) reads only last maxLines lines now

It should speed up and reduce memory consumption for some plugins (i.e.
Email-ext Plugin).
Also now this method could be used to get last lines of build output in efficient manner.

* Fix issues from code review

[FIXED JENKINS-39454] Do not consider pendings when deciding whether a schedule result should be new or existing, as we have already taken a snapshot of actions. (#2609)

[FIXED JENKINS-38487] - Jenkins startup must not fail in the case of ComputerListener failure (#2610)

Without this code Jenkinbs startup fails if EnvInject fails to find global property file on startup.

Javadoc says "Exceptions will be recorded to the listener. Note that throwing an exception doesn't put the computer offline." regarding the listener method exception, hence we should not block Jenkins startup

[JENKINS-39414] Stapler 1.247

[FIXED JENKINS-39404] Restore symmetry by adding removeAction and removeActions methods to Actionable

[JENKINS-39404] Clarify the lack of transaction support and consequent effect on concurrent operations

- cannot use a local variable as the optimization only applies while we have not found the action being added

- We cannot modify `replaceAction` to return the dirty flag, in fact most callers probably don't care... but if you do care, we now provide `addOrReplaceAction`
- Clarify the javadocs to reflect that these methods are not going to affect actions added by transient action factories

[JENKINS-39404] We cannot change these to return a boolean, but doesn't matter because they would always return `true`

I would need to use <A super Action> which would allow Object.class

[FIXED JENKINS-39404] Restore symmetry by adding removeAction and removeActions methods to Actionable

Update the detached version of Maven plugin to 2.14