Add an integration test module + joda time

[Vlatombe]

in some scenarios joda time version is required because different
plugins pull different versions.

Require upper bound dependencies error for joda-time:joda-time:2.10.2 paths to dependency are:
+-io.jenkins.tools.bom:sample:999999-SNAPSHOT
  +-org.jenkins-ci.plugins:dashboard-view:2.17
    +-joda-time:joda-time:2.10.2
and
+-io.jenkins.tools.bom:sample:999999-SNAPSHOT
  +-io.jenkins.configuration-as-code:test-harness:1.54
    +-com.github.erosb:everit-json-schema:1.13.0
      +-com.damnhandy:handy-uri-templates:2.1.8
        +-joda-time:joda-time:2.10.2 (managed) <-- joda-time:joda-time:2.10.10
and
+-io.jenkins.tools.bom:sample:999999-SNAPSHOT
  +-org.jenkinsci.plugins:pipeline-model-definition:1.9.2
    +-org.jenkinsci.plugins:pipeline-model-api:1.9.2
      +-com.github.fge:json-schema-validator:2.0.4
        +-joda-time:joda-time:2.10.2 (managed) <-- joda-time:joda-time:2.1

On the kubernetes plugin for example, I don't have dashboard-view and the two others (pipeline-model-extensions and io.jenkins.configuration-as-code:test-harness) conflict.

I was planning initially to convert the sample-plugin to an its, however since the current logic to set up pct highly depends on it and I wasn't sure of what I was doing, I preferred to keep it as is.

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

[jglick]

joda time version is required because different plugins pull different versions

Then a library wrapper module should be introduced.

[jglick]

We do not want to include random libraries here—only plugins.

[jglick]

Filing #683 for the IT thing. I would like to replace sample-plugin, not just augment it.

[Vlatombe]

Fine

[MarkEWaite]

I thought that Joda time was considered obsolete with Java 8 and later. In those cases where we have capacity to do so, shouldn't we push to replace Joda time with JSR-310 as included in Java 8?

[timja]

Yes joda-time shouldn’t be used anymore, but depends on if dependencies will remove it

[Vlatombe]

From the tree above it could probably be cleaned up from dashboard-view.