build: remove TestBench dependencies from the published POM

[javier-godoy]

Mark the TestBench dependencies as <?dev-only?> and add dev-nuke-maven-plugin, so that they are removed from the published POM.

Reference: FlowingCode/CommonsDemo@ab627d1

See https://github.com/FlowingCode/AddonsInternal/issues/214
See https://github.com/FlowingCode/AddonsInternal/issues/215

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated build and development tooling; no user-facing changes.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 97e59fbd-2cd0-49c4-a587-20ab0757fb6f

📥 Commits

Reviewing files that changed from the base of the PR and between 2980991 and 263a832.

📒 Files selected for processing (1)

• pom.xml

 ________________________________________________________________________________
< This conditional is a choose-your-own-adventure where every choice is 'panic'. >
 --------------------------------------------------------------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[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