Ensure cleanupQuery gets called for procedures

[findepi]

Ensure cleanupQuery is called for cases when ConnectorMetadata is constructed outside of typical query processing
(Connector.getMetadata).

[findinpath]

We have an increasing number of tweaks in the procedures:

• try (ThreadContextClassLoader ignored = new ThreadContextClassLoader(getClass().getClassLoader())) { ....}
• try (UncheckedCloseable ignore = () -> metadata.cleanupQuery(session)) { .... }

I'm not sure how the engineers maintaining eventually the procedure code/ writing new procedures are supposed to know about them.
Ideally they would be transparent for the the procedure developer, but i don't see a better solution currently.

[mosabua]

No release notes entry needed @findepi @findinpath @ebyhr ?

[findinpath]

No release notes entry needed @findepi @findinpath @ebyhr ?

Hive
Perform cleanup of resources after executing procedures

[findepi]

Hive
Perform cleanup of resources after executing procedures

@findinpath please try to think in end-user's terms.
Try to say why a user should care, and when. If we cannot make user excited about given change, we should omit from Release Notes.

[mosabua]

@findepi @findinpath .. so maybe we say something like "Prevent memory leak" or "Increase stability" .... or it really is not user facing enough and we decide to leave out .. one way or another.. please let me know

[findinpath]

If we cannot make user excited about given change, we should omit from Release Notes.

I'd say that at the moment it is not user facing.