GEOS-9535 Update Oracle JDBC driver

[mprins]

Upgrade the Oracle JDBC driver to the latest version hosted on Maven Central, add the "Oracle Free Use Terms and Conditions" (FUTC), remove the now defunct oracleDriver profile

see:

• GEOS-9535
• GEOT-6529 Update Oracle JDBC driver geotools/geotools#2832

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 following are required only for core and extension modules (they are welcomed, but not required, for community modules):

• There is a ticket in Jira describing the issue/improvement/feature (a notable exemptions is, changes not visible to end users)
• PR for bug fixes and small new features are presented as a single commit
• Commit message must be in the form "[GEOS-XYZW] Title of the Jira ticket" (export to XML in Jira generates the message in this exact form)
• 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.
• 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)
• Commits changing the UI, existing user workflows, or adding new functionality, need to include documentation updates (screenshots, text)
• Committs changing the REST API, or any configuration object, should check it the REST API docs (Swagger YAML files and classic documentation) need to be updated.

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]

I am excited for the change, anything to make oracle easier.

This was discussed in today's meeting, noting the STRUCT --> OracleStruct change we are not going to be able to backport.

[mprins]

This was discussed in today's meeting, noting the STRUCT --> OracleStruct change we are not going to be able to backport.

I understand that for Geotoos there is a minor API change from a concrete class to the interface of that class, but I think for Geoserver this can be backported since basically the only functional change here is that the oracle driver is added to the extension

[mprins]

I've sent in a new CLA for B3Partners

[aaime]

The GeoTools portion is all merged, this one should also be good to go, merging.