Catch SQLException when calling JDBC API from agent

[SylvainJuge]

What does this PR do?

This is an improvement on the previous fix #1006 that wraps all calls made by the agent to make sure that:

• any thrown SQLException will mark the JDBC feature as not supported for the JDBC implementation.
• avoid to trigger excessive logging and throwing exceptions at each JDBC call

Checklist

• My code follows the style guidelines of this project
• I have rebased my changes on top of the latest master branch
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• New and existing [unit tests](https://github.com/elastic/apm-agent-
• I have updated CHANGELOG.asciidoc
• I have updated supported-technologies.asciidoc
• Added an API method or config option? Document in which version this will be introduced
• Added an instrumentation plugin? How did you make sure that old, non-supported versions are not instrumented by accident?

Author's Checklist

• test for Statement.getUpdateCount that might not be supported Span isn't closed if JDBC implementation errors on the getUpdateCount method #1006
• test for Statement.getConnection that might return null (unlikely, but possible)
• test for Connection.getMetadata that might return null (unlikely, but possible)

Related issues

• Closes I am getting java.sql.SQLFeatureNotSupportedException and I can not see the query transaction. #1025
• Relates Span isn't closed if JDBC implementation errors on the getUpdateCount method #1006

[felixbarny]

Please test for potential performance degradation before merging