FileSchemaHistory can lead to OutOfMemory exceptions when working with large schema history files [DBZ-9484]

Migrated from [DBZ-9484](https://issues.redhat.com/browse/DBZ-9484)

In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.
h1. Bug report

For bug reports, provide this information, please:
h2. What Debezium connector do you use and what version?

<2.5.2>
h2. What is the connector configuration?

<

snapshot.mode=initial
max.queue.size=81290
max.batch.size=20480
snapshot.max.threads=2
snapshot.transaction.isolation=read_committed
snapshot.locking.mode=none
incremental.snapshot.chunk.size=2000
snapshot.fetch.size=1000
snapshot.transaction.isolation=read_committed

>
h2. What is the captured database version and mode of deployment?

(E.g. on-premises, with a specific cloud provider, etc.)

h2. What behavior do you expect?

h2. What behavior do you see?

<
* Using a CDCCapture node with a huge Oracle DataBase is causing the JVM in the Integration Server to crash even with a very large JVMMaxHeapSize. I tried tuning the JVM Stack Size for the customer to see if it would reduce the overall heap size, but it did not help. Customer currently has the JVMMaxHeapSize set to 12 GB, and it is crashing with a JVM Out of Memory after about 12 hours.

OOM happening after 12 hours>
h2. Do you see the same behaviour using the latest released Debezium version?

(Ideally, also verify with latest Alpha/Beta/CR version)

h2. Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide [DEBUG/TRACE|https://debezium.io/documentation/reference/stable/operations/logging.html] level log)

h2. How to reproduce the issue using our [tutorial|https://github.com/debezium/debezium-examples/tree/main/tutorial] deployment?

h1. Feature request or enhancement

For feature requests or enhancements, provide this information, please:
h2. Which use case/requirement will be addressed by the proposed feature?

h2. Implementation ideas (optional)

Start by locating FileSchemaHistory and tracing its use from OracleConnector while reproducing the large-schema-history scenario. The issue provides no logs, reproduction steps, named tests, or implementation location; done means preventing the reported JVM OutOfMemory crash with large schema history files.

Written by the indexing model from the issue text.