[NATS] Extend to support in-memory stream

[kevin-ip]

Motivation

While I was benchmarking NATS, I found myself needed to benchmark its in-memory stream.
Think it would be beneficial to other folks with the option.

Changes

Extend NatsConfig with storageType and maxBytes to support in-memory stream while limiting memory consumption.

[kevin-ip]

Test failed on driver-kop, any idea?

Error:  Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M7:test (default-test) on project driver-kop: 
Error:  
Error:  Please refer to /home/runner/work/benchmark/benchmark/driver-kop/target/surefire-reports for the individual test results.
Error:  Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
Error: [ERROR] There was an error in the forked process
Error:  'java.lang.ClassLoader[] org.apache.logging.log4j.util.LoaderUtil.getClassLoaders()'
Error:  org.apache.maven.surefire.booter.SurefireBooterForkException: There was an error in the forked process
Error:  'java.lang.ClassLoader[] org.apache.logging.log4j.util.LoaderUtil.getClassLoaders()'
Error:  	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:701)

see also https://github.com/openmessaging/benchmark/actions/runs/4309206859/jobs/7905914983

[merlimat]

@BewareMyPower Can you take a look at the KoP driver build failure?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 5 days if no further activity occurs. Thank you for your contributions.

[BewareMyPower]

@merlimat Sorry it seems that I missed the comment before. Here is the fix: #387