Unify prop files for builds and production

[niloc132]

Fixes #1732

[devinrsmith]

Happy with structural changes. Happy to change defaults, as long as we are aware of what's changing.

[devinrsmith]

Remind me, what happens at exhaustion? Do we throw exception, or schedule for next available thread.

[rcaudy]

We shutdown the process.

[rcaudy]

That said, we shouldn't be using this thread pool much anymore.

[niloc132]

This was included in grpc-api.prop to begin with because the server wouldnt start without it. Startup today without that:

Initiating shutdown due to: Uncaught exception in thread UpdateGraphProcessor.DEFAULT.refreshThread
io.deephaven.configuration.PropertyException: Missing property in config file: NIO.driver.maxThreadCount
        at io.deephaven.configuration.PropertyFile.getProperty(PropertyFile.java:115)
        at io.deephaven.configuration.PropertyFile.getInteger(PropertyFile.java:126)
        at io.deephaven.net.impl.nio.NIODriver.init(NIODriver.java:106)
        at io.deephaven.net.impl.nio.NIODriver.init(NIODriver.java:96)
        at io.deephaven.net.CommBase.getScheduler(CommBase.java:68)
        at io.deephaven.engine.updategraph.UpdateGraphProcessor.refreshTablesAndFlushNotifications(UpdateGraphProcessor.java:1457)
        at io.deephaven.engine.updategraph.UpdateGraphProcessor$1.run(UpdateGraphProcessor.java:208)

[niloc132]

So, the important thing here is that dh-defaults.prop was only used for some tests and some codegen, but was never used at runtime by our running containers.

I have re-run all generators and there is no changes as a result of this to our .java or .py files.

The py tests were inconsistent before and some had broken paths, which is what prompted this change to begin with.

My assumption is that since workers have always* used the grpc-api.prop file's contents and we've never used dh-defaults.prop in any engine unit test or running container, that we would prefer the contents of grpc-api.prop, though we like the name of dh-defaults.prop better.

* since we ran a grpc server at all

[devinrsmith]

Ah - I missed the part where you were taking the existing values from grpc-api.prop.

I think our defaults are due for an audit, but no reason to hold up this good structural change.

[rcaudy]

That said, we shouldn't be using this thread pool much anymore.