fix: use parameter generateTimestamp to suppress timestamp in @Genera…

[anessi]

Description

Use parameter generateTimestamp to suppress timestamp in @Generated annotation, see #433

Related issue(s)
Fixes #433

[cdm-phm]

I really like this option but maybe it would be better the current behaviour as default and make it opt-in, especially if it is for a patch release. Also, parameters should be listed in the README.

[anessi]

Added a default value for generateTimestamp and set it to true. The parameter is now listed in the README and can be changed by adding -p generateTimestamp=false on the CLI.

[Tenischev]

@anessi Thank you for the contribution!
Could you please add a new test case for your parameter to the parameters.test.js?

[anessi]

I added 2 tests.
As mentioned in the other PR I had serious troubles running the tests reliably. This seems to be a known problem: https://stackoverflow.com/questions/76203449/a-jest-worker-process-was-terminated-by-another-process

I suggest to update the README.md with the following notes:

• Running the tests sequentially: npm test -- --runInBand --no-cache
• Running the tests with Docker: docker run --rm -it -v "$PWD":/app -w /app node:24 bash -c "npm install && npm test -- --runInBand --no-cache"
• Running a single test: npm test -- --runInBand --no-cache -t "should include timestamp in @Generated annotation when generateTimestamp is true"

This will help Java devs that are not very familiar with Node.