SDN-R goes Sodium and Java11

Infrastructure Jenkins => Check
Migration strategy BingBäng vs. Smooth => Specify
- SDNC should completely move to J11
- CCSDK ... J8 and J11?
ODL Base image with J11

	Solution 1 (versioning)	Solution 2(artifcat-suffix)
	ccsdk-parent (version): neon java 8: 2.0.0 neon java 11: 2.0.0-SNAPSHOT (Test) sodium java 11: 2.0.1 features: neon java 8: 1.0.X sodium java 11: 1.1.X	ccsdk-parent (artifactId): java 8: unchanged java 11: <artifactId>-j11 features: java 8: unchanged java 11: <artifactId>-j11
this has impacts on		docker image names: sdnc-j11-image
pros	Java code and libs are compatible	Piece by piece migration path
cons	Java code and libs are compatible	different artifacts with same function in nexus feature names for container to start will be renamed
open points		neon version code compatible with sodium j8?

Using ODL hints from here: https://docs.opendaylight.org/en/stable-sodium/release-notes/upgrade-process.html#datacontainer-implementedinterface-is-type-narrowed-in-dataobjects
- POM change: JSR305: Use google findbugs
Using ODL Parents
JDK: openJDK 11
Dev environment for J8 and J11 (for older releases)
Most changes are in POM files
A few changes are in the code.

oauth2 removed
- https://jira.opendaylight.org/browse/AAA-173
- Who is using this?
- How to replace?