feat(wadm)!: support configuring max stream bytes

[brooksmtownsend]

Feature or Problem

This PR surfaces additional command line flags & environment variables for configuring the creation of NATS streams and KV buckets with a maximum amount of bytes. By default there is no limit, but depending on the NATS deployment, operators may want to (or need to) supply this parameter.

I hid these variables by default because they are very verbose, but I plan on referencing them in documentation.

Related Issues

Release Information

Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

[ahmedtadde]

hey @brooksmtownsend if time permits, can you please give a brief on what instigated this change. On the surface, it seems like just a prudent thing to do, which is totally fine. Just curious if this a precursor to something else that's coming up or a fix for something.

[brooksmtownsend]

Ah @ahmedtadde yep! Mostly what instigated this was #417, we had a dev in the wasmCloud slack who wanted to use https://www.synadia.com/ for their NATS infrastructure and you have to supply the max_bytes parameter for creating the streams. It would probably be helpful to have a script that creates these streams based on this configuration so you can pre-create the streams in any NATS infra. The key discovery here too was that we can reuse the existing stream, so creating ahead of time will work just fine