Decouple release of create-*-app packages from @inditextech-scoped packages

## Summary
Currently `nx release` versions and publishes **all** packages under `code/packages/*` together, using a single fixed version (e.g. `5.3.0-SNAPSHOT`). This ties the unscoped scaffolding CLIs `create-weave-backend-app` and `create-weave-frontend-app` to the exact same release cadence and version number as the `@inditextech`-scoped SDK packages (`@inditextech/weave-sdk`, `@inditextech/weave-react`, `@inditextech/weave-types`, etc.), even though the two groups have very different release needs: the CLIs mostly change to update scaffolded templates/dependencies, while the SDK packages change with core framework work.

We should decouple releases so that `create-weave-backend-app` and `create-weave-frontend-app` can be versioned and published independently from the `@inditextech`-scoped packages.

### Motivation
**Reduce release noise**: publishing a new version of `create-weave-backend-app`/`create-weave-frontend-app` on every SDK release (and vice versa) creates unnecessary npm publishes, changelog entries, and git tags for packages that had no functional change.

Start by locating the nx release configuration that versions and publishes packages under code/packages/*. Trace how the two create-*-app packages are grouped with the @inditextech-scoped packages, then verify that each group can be versioned and published on its own without unnecessary releases for the other group.

Written by the indexing model from the issue text.