build: add nebula.release versioning and dependency locking

[soloturn]

Adds the same versioning/locking setup TerasologyLauncher already uses.

• nebula.release 21.0.0 for git-tag-driven versioning. This project already tags releases as vX.Y.Z (v5.1.0 latest), matching the plugin's default tag convention, so no extra tagStrategy config is needed.
• Buildscript-classpath dependency locking (activateDependencyLocking() on the buildscript classpath), producing buildscript-gradle.lockfile.
• dependencyLocking { lockAllConfigurations() } on every subproject (cr-core, cr-destsol, cr-terasology), each with its own gradle.lockfile — locking is per-project, so a single shared lockfile isn't how Gradle does this for a multi-project build. The root project has no resolvable configurations of its own beyond buildscript, so it only gets the buildscript lockfile.
• Same -PnoLock escape hatch as the launcher: passing it skips dependencyLocking{} entirely for that build, letting every range resolve fresh against whatever satisfies it right now — useful for trying an update locally before committing to it via --write-locks.

Test plan:

• ./gradlew build -x test succeeds with locking active
• Lockfiles generated via ./gradlew dependencies --write-locks (root) and ./gradlew :cr-core:dependencies :cr-destsol:dependencies :cr-terasology:dependencies --write-locks (subprojects)

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0a055da6-4719-4f42-801a-7a88e1f9ed27

---

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.}