publish-plugin: Change naming for timeout settings

The naming is misleading. RetryingConfig + maxRetries means the plugin would retry publication multiple times, however, in practice it means it would “just wait the specified number of times while the repository is in progress”.

Do you think it would be better to use timeout-like configuration properties?

For instance connectToNexusTimeout, initializeRepositoryTimeout, singleArtifactPublishTimeout, closeRepositoryTimeout, etc, etc.

Note: the users do not care what the number of “status check” attempts is there. What they care is overall timeout value, and they might want to have something like initial delay between status check attempts.

WDYT?

Original comment from @vlsi in closed #18 .

I think that it’s really nice idea and I don’t want it forgot in closed PR. My current timeout settings look like:

nexusPublishing {
    ...
    clientTimeout.set(Duration.parse("PT10M")) // 10 minutes
}
nexusStaging {
    ...
    numberOfRetries = 360 // 1 hour if 10 seconds delay
    delayBetweenRetriesInMillis = 10000 // 10 seconds
}

But really I just want to configure, that I’m ready to wait 1 hour for publishing staging repository. Something like a configuration timeout for publishing artifacts to the staging repository in nexusPublishing block.