Fix build caching: remove generateSecretKeys dependency from test

[ribafish]

Summary

The test task depends on generateSecretKeys, which writes new random values to framework/security/config/security.properties on every build. Since this file is part of the main resource source set (config/ dirs are included via getDirectoryInActiveComponentsIfExists('config')), changing it causes cascading Gradle build cache misses for:

• :compileTestGroovy — classpath includes main resources
• :checkstyleMain — classpath includes sourceSets.main.output
• :checkstyleTest — same reason
• :test — classpath + test classes differ

This PR:

1. Removes dependsOn 'generateSecretKeys' from the test task — the main security.properties is no longer mutated during build
2. Adds a test-specific security.properties in framework/security/src/test/resources/ with fixed keys — this shadows the main config on the test classpath so unit tests that require JWT keys (e.g. ModelFormTest) continue to work

The generateSecretKeys task is unchanged and remains available for manual use (./gradlew generateSecretKeys) and as a dependency of loadAll.

[jacopoc]

Hi @ribafish,
your report is valid, but I addressed it using a different strategy than the one you proposed.

I’ve merged my changes in PR #1029.
Please take a look and let me know if this resolves the issues you were experiencing.

Thank you!

[ribafish]

Thanks for the quick fix in #1029!

It does resolve the issue for local build cache reuse (two consecutive builds on the same machine) — the first build generates keys, the second sees them and skips.

However, it doesn't fully address cross-machine build cache reuse. On a fresh checkout the keys are empty, so generateSecretKeys still generates random values and mutates security.properties. Two different machines checking out the same commit will each generate different random keys, producing different processResources output and different cache keys for :compileTestGroovy, :checkstyleMain, :checkstyleTest, and :test.

This PR complements #1029 by removing generateSecretKeys from the build task graph entirely (it remains available for manual use and loadAll), and providing fixed test keys via a test resource file so that security.properties is never mutated during builds.