Make SqlDelightWorkerTask more configurable, and update default configuration to support developing on Windows

[MSDarwish2000]

Migration to process isolation in #5068 resulted in broken migration verification, and plugin actions on Windows. This is due to JDBC's usage of temporary directory which cannot be retrieved from environment variables as they are, deliberately or by mistake, not passed to isolated process by default.

This PR makes SqlDelightWorkerTask more configurable by exposing properties like environment, maxHeapSize, ...etc. It also sets the "convention" value of these properties so that developing on Windows is no longer broken. It also may fix Out of memory. Java heap space exceptions on other machines.

Fixes #5129

[MSDarwish2000]

During further tests, I found that process isolation also results in

Out of memory. Java heap space

It can be fixed by passing through JvmArgs, which may result in unexpected consequences, passing predefined heap size, or reverting the process isolation.

I've opted for fixed 2GB max heap size.

Also, implementing CI tests for this situation to prevent recurrence would be great.

[MSDarwish2000]

I've made the task more configurable by adding environment, systemProperties, minHeapSize, maxHeapSize, and jvmArgs. I've made environment inherit inheritable env variables from its parent similar to how DefaultJavaForkOptions handle it. Also, I've set the default value of maxHeapSize to 512MB which handles my average database well, and it is configurable for larger projects. Also, I've set defaultCharacterEncoding to "UTF-8"

A further step would be to implement ClassLoaderWorkerSpec and JavaForkOptions and implement the remaining properties, or ProcessWorkerSpec and hide the forkOptions behind an additional property.

I'd appreciate your review since this affects the API a lot.