Investigate whether StreamDBClient is closed inside ArchiveQuery

[StrongestNumber9]

Describe the bug

Investigate whether StreamDBClient is closed inside ArchiveQuery

Expected behavior

Should be closeable like KafkaQuery

How to reproduce

Screenshots

Software version

Desktop (please complete the following information if relevant):

• OS:
• Browser:
• Version:

Additional context

#334
#332
#278

[StrongestNumber9]

Seems like StreamDBClient implements AutoCloseable but it is not explicitly stopped at any point, and ArchiveQuery interface does not have close() method which means ArchiveMicroStreamReader.close() won't be able to call sdc.stop() inside ArchiveQueryProcessor

pth_06/src/main/java/com/teragrep/pth_06/ArchiveMicroStreamReader.java

Lines 200 to 215 in 826a9f0

	@Override
	public void stop() {
	LOGGER.debug("ArchiveMicroStreamReader.stop called");
	if (this.config.isKafkaEnabled) {
	try {
	kq.close();
	}
	catch (final IOException exception) {
	LOGGER
	.error(
	"Error closing kafka query while calling stop() with message <{}>",
	exception.getMessage()
	);
	}
	}
	}

pth_06/src/main/java/com/teragrep/pth_06/planner/ArchiveQueryProcessor.java

Line 78 in 826a9f0

private final StreamDBClient sdc;

pth_06/src/main/java/com/teragrep/pth_06/planner/StreamDBClient.java

Lines 330 to 341 in 826a9f0

	@Override
	public void close() {
	try {
	if (connection != null && !connection.isClosed()) {
	connection.close();
	LOGGER.debug("Closed JDBC connection");
	}
	}
	catch (final SQLException e) {
	LOGGER.warn("Error closing JDBC connection: <{}>", e.getMessage());
	}
	}

Logs shows that it is closed inside tests but I can't tell for certain how it works in real world queries