grails-databinding publication fails with --rerun-tasks

## Description

Running targeted Grails Forge tests and packaging with `--rerun-tasks` from the `grails-forge` composite build fails while publishing the included `grails-databinding` project because its generated `grails-plugin.xml` artifact is missing.

The same targeted Forge command succeeds without `--rerun-tasks`.

## Reproduction

From the `grails-forge` directory on the `7.0.x` branch:

```shell
./gradlew grails-forge-api:test grails-forge-web-netty:test grails-forge-web-netty:awsElasticBeanstalk --rerun-tasks
```

## Actual behavior

The build fails at:

```text
:grails-core:grails-databinding:publishMavenPublicationToTestCaseMavenRepoRepository
```

with:

```text
Invalid publication 'maven': artifact file does not exist:
grails-databinding/build/classes/groovy/main/META-INF/grails-plugin.xml
```

The failure occurs before the requested Forge tests and package verification can complete.

## Expected behavior

Forcing task execution should regenerate `META-INF/grails-plugin.xml` before the publication task consumes it, allowing the composite build and requested Forge tasks to complete.

## Additional information

- Branch: `7.0.x`
- Gradle: 8.14.5
- Local runtime used for reproduction: Amazon Corretto 21.0.11
- Operating system: Windows 11
- The targeted command passes when `--rerun-tasks` is removed.
- No `grails-databinding` source changes were present during reproduction.

From the grails-forge directory on the 7.0.x branch, run the reported Gradle command with --rerun-tasks and inspect the grails-databinding publication task. Trace how grails-databinding/build/classes/groovy/main/META-INF/grails-plugin.xml is generated and consumed. Done means the artifact exists before publication and the targeted Forge tests and package verification complete successfully.

Written by the indexing model from the issue text.