This closes #11936.

This reverts commit 0341b4a8.

The test doesn't work because it has hard-coded paths to the local
machine where the test snapshot data was created in the snapshots.

The patch also adds a new SourceEventType of NoMoreSplitsEvent to allow the SourceReaderBase to exit after all the work is done.

This closes #11920.

The caching is overly aggressive and potentially even ignores changes to the .yml files.

We need this for future changes to the serialization format.

This reverts commit 339f5d84.

I'm reverting these three related commits because it is important to
have confidence in our testing and to clearly separate the addition of
the Bucket State upgrade test from changing the serializer.

This reverts commit f850ec78.

I'm reverting these three related commits because it is important to
have confidence in our testing and to clearly separate the addition of
the Bucket State upgrade test from changing the serializer.

This reverts commit 547c168a.

I'm reverting these three related commits because it is important to
have confidence in our testing and to clearly separate the addition of
the Bucket State upgrade test from changing the serializer.

After #9747, managed memory is allocated from UNSAFE, not as direct nio buffers as before 1.10.
The releasing of segments released also underlying unsafe memory which is dangerous in general
as there can be still references to java objects giving access to the released memory. If this reference
ever leaks, the illegal memory access can result in memory corruption of other code parts w/o even segmentation fault.

The solution can be similar to how Java handles direct memory limit:
- underlying byte buffers of segments are registered to phantom reference queue with a Java GC cleaner which releases the unsafe memory
- all allocations and reservations are managed by a memory limit and an atomic available memory
- if available memory is not enough while reserving, the phantom reference queue processing is triggered to run hopefully discovered by GC cleaners
- memory can be released directly or in a GC cleaner

The GC is also sped up by nulling out byte buffer reference in `HybridMemorySegment#free` which is inaccessible anyways after freeing.
Otherwise also a lot of tests, which hold accidental references to memory segments, have to be fixed to not hold them.
The `MemoryManager#verifyEmpty` checks that everything can be GC'ed at the end of the tests and
after slot closing in production to detect memory leaks if any other references are held, e.g. from `HybridMemorySegment#wrap`.

This closes #11109.

Document command line options for the 'lein run test' command.

In the Docker section, add that DataStreamAllroundTestProgram must be
built first.

Add details about types/roles of nodes and minimum number of nodes
required.

This closes #12019.

Make ssh-keygen output private key in PEM format so that Jsch does not
complain about wrong private key format.

This closes #12168

This closes #12134

This change includes two things:
1. Make the PartFileWriter generic and decouple the PartFileWriter and RecoverableStream. According to different pre-commit / commit methods,
this change allows us to extend different types of PartFileWriter.
2. Make the Bucket/Buckets depends on the PartFileFactory instead of RecoverableWriter.

This closes #12132

Generated hash aggregate code may produce NPE in some cases existing an aggregate call with Filter.

This closes #12119

This closes #11854.

[hotfix] Add setupFlinkConfig to KubernetesTestBase to make sure flinkConfig is always setup before used

[FLINK-17764][Examples] Update tips about the default planner to blink when the planner parameter value is not recognized

This closes #12194.

This closes #12184

This closes #12073