fix: Build should not depend on prepare

[caalador]

Running the build frontend task
should not depend on the prepare
task so that the tasks do not
break each others caching.

part of #17354

[github-actions]

Test Results

 1 386 files  ±0   1 386 suites  ±0   1h 30m 7s ⏱️ + 1m 23s
 9 911 tests ±0   9 840 ✅ ±0  71 💤 ±0  0 ❌ ±0 
10 384 runs  ±0  10 304 ✅ ±0  80 💤 ±0  0 ❌ ±0 

Results for commit 9d3a212. ± Comparison against base commit 7163d37.

♻️ This comment has been updated with latest results.

[mcollovati]

Works as expected with Gradle daemon, but it causes issues without.
Without the daemon, the flow-build-info.json file is deleted after the first build; the next build will not run vaadinBuildFrontend and produce an artifact without flow-build-info.json causing issues at runtime, since the app starts in development mode.

[caalador]

Seems we would need to come up with a new clean up strategy for the token file after a production build as this will not work as expected for the incremental build.

[caalador]

Moved the token clean up to the respective plugins to handle.

[mcollovati]

For Maven, I pushed #23945, that postpones the delete to the end of the build session. It works only if the plugin is configured as an extension, but it should help when using mvnd.

For Gradle, my concern is that using doLast could impact incremental build on our or other plugins (e.g. Jar), causing the next run to not be up to date. But let's try and see how this goes.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
2572 New issues
1 Accepted issue

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud