[Bug]: Java portable SDK should enable heap dumping with HeapDumpOnOutOfMemoryError if configured

### What happened?

Currently the MemoryMonitor dumps heap if it detects GC thrashing.
However if the JVM ooms all of a sudden it doesn't trigger a heap dump and thus there are not observable even if newly added EnableHeapDumps is set.

The container boot should examine if this option is set and if so configure the jvm when launching to dump heap on oom, see https://www.baeldung.com/java-heap-dump-capture#automatically

### Issue Priority

Priority: 2 (default / most bugs should be filed as P2)

### Issue Components

- [ ] Component: Python SDK
- [X] Component: Java SDK
- [ ] Component: Go SDK
- [ ] Component: Typescript SDK
- [ ] Component: IO connector
- [ ] Component: Beam examples
- [ ] Component: Beam playground
- [ ] Component: Beam katas
- [ ] Component: Website
- [ ] Component: Spark Runner
- [ ] Component: Flink Runner
- [ ] Component: Samza Runner
- [ ] Component: Twister2 Runner
- [ ] Component: Hazelcast Jet Runner
- [ ] Component: Google Cloud Dataflow Runner