Use -XX:CMSInitiatingOccupancyFraction

Right now, we don't set the `-XX:CMSInitiatingOccupancyFraction` option. For very long running KSQL processes, it has been observed that the heap utilization gets very close to the limit before CMS is kicked off.

It would be good add the following options to the start command for ksql:

`-XX:CMSInitiatingOccupancyFraction=60 -XX:+UseCMSInitiatingOccupancyOnly`

This will ensure more predictable heap usage.

Start with the ksql start command and identify where its JVM options are assembled. Add the two options named in the issue, then verify that the resulting command includes them and that the setting applies to long-running KSQL processes.

Written by the indexing model from the issue text.