Pass --ram flag to database finalize

[edoardopirovano]

This PR passes a RAM option to database finalize, using the same logic to determine what value to use as we do for database run-queries. Currently, without a RAM option the JVM will determine it's own limit which is much more conservative than what we would do (i.e. use most of the memory available) leading to OOM errors during TRAP import for certain projects.

Merge / deployment checklist

• Confirm this change is backwards compatible with existing workflows.
• Confirm the readme has been updated if necessary.
• Confirm the changelog has been updated if necessary.

[edoardopirovano]

@cklin I opted for only using this option with CLI versions >=2.5.9 as, if I recall correctly, the flag was introduced in 2.5.8 but had a bug at that point. Is this correct?

[henrymercer]

Looks good modulo the discussion on the correct CodeQL version to check for before passing this flag.

[cklin]

@cklin I opted for only using this option with CLI versions >=2.5.9 as, if I recall correctly, the flag was introduced in 2.5.8 but had a bug at that point. Is this correct?

The bug fix https://github.com/github/semmle-code/pull/39696/commits/14b72e0439866c662cfdc1a9176ffad23b10a048 went into 2.5.8. And of course 2.5.9 works too.

[edoardopirovano]

@cklin I opted for only using this option with CLI versions >=2.5.9 as, if I recall correctly, the flag was introduced in 2.5.8 but had a bug at that point. Is this correct?

The bug fix github/semmle-code@14b72e0 went into 2.5.8. And of course 2.5.9 works too.

Ah, okay, we can use 2.5.8 then! Thanks for checking that 🙂