chore: fix CI by removing examples module; remove *.db files from tests module

[ricardozanini]

In this PR:

• Correcting the sample workflow set-listen-to-any.yaml so a listen actually waits (not completes immediately due to listen.any: []).
• Generating DB samples at test time (under @TempDir) instead of committing binary DB files.
• Making the restore tests parameterized.
• Adding deterministic awaits in the DB generator to eliminate race conditions.
• Remove examples from release mvn command.

Follow up:

• To check if the desired behavior is to finish the workflow immediately on listen.to.any: []. I believe that's the desired behavior, but it's worth checking out.

Not sure how the DbGenerator was working before, since the sample workflow was completed immediately/having a racing condition before suspending/finishing the workflow by listening to anything empty.

I created a small/raw/workaround to run the generator on a separate JVM when running the tests to avoid a collision with the file read. It's working pretty good, if you have a better idea (or any changes in the store implementation to avoid this), let me know.

[fjtirado]

I do not get why storing binary file is worse than spawning a new JVM.
Also the DB files were stored on purpose to check backward compatibility with previous DB versions. They are intentionally NOT generated with every run
In my opinion this PR should just contain changes on release.yaml, pom.xml (to not run the examples) and comment main method of DBGenerator.