GEOT-6529 Update Oracle JDBC driver

[mprins]

Upgrade the Oracle JDBC driver to the latest version hosted on Maven Central, fix any deprecations caused by the driver upgrade.

Also factor out all Oracle deprecations, notably any use of:

• oracle.sql.STRUCT
• oracle.sql.ARRAY
• oracle.sql.StructDescriptor
• oracle.sql.ArrayDescriptor

Make sure to use the proper driver classname, which is oracle.jdbc.OracleDriver, as well as some javadoc fixes and some replacement of StringBuffer by StringBuilder for improved performance.

Ignore/Disable Oracle3DOnlineTest#testBBOX3DOutsideLine() as even in plain SQL it seems to fail

Add a note to use the proper oracle driver class name in the upgrade notes

see GEOT-6529

Geoserver followup: geoserver/geoserver#4119

Checklist

Reviewing is a process done by project maintainers, mostly on a volunteer basis. We try to keep the overhead as small as possible and appreciate if you help us to do so by completing the following items. Feel free to ask in a comment if you have troubles with any of them.

For all pull requests:

• Confirm you have read the contribution guidelines
• You have sent a Contribution Licence Agreement (CLA) as necessary (not required for small changes, e.g., fixing typos in documentation)
• Make sure the first PR targets the master branch, eventual backports will be managed later. This can be ignored if the PR is fixing an issue that only happens in a specific branch, but not in newer ones.
• The changes are not breaking the build in downstream projects using SNAPSHOT dependencies, GeoWebCache and GeoServer.

The following are required only for core and extension modules (they are welcomed, but not required, for unsupported modules):

• There is an issue in Jira describing the bug/task/new feature (a notable exemptions is, changes not visible to end users). The ticket is for the GeoTools project, if the issue was found elsewhere it's a good practice to link to the origin ticket/issue.
• The pull request contains changes related to a single objective. If multiple focuses cannot be avoided, each one is in its own commit and has a separate ticket describing it.
• PR for bug fixes and small new features are presented as a single commit
• Commit message must be in the form "[GEOT-XYZW] Title of the Jira ticket"
• New unit tests have been added covering the changes
• This PR passes all existing unit tests (test results will be reported by travis-ci after opening this PR)
• This PR passes the QA checks (QA checks results will be reported by travis-ci after opening this PR)
• Documentation has been updated accordingly.

Submitting the PR does not require you to check all items, but by the time it gets merged, they should be either satisfied or inapplicable.

[jodygarnett]

Looks good, I note some upgrade instructions will be needed for the geotools manual.

[mprins]

I've sent in a new CLA for B3Partners

[aaime]

Merged, thanks!