Automate Community npm releases (#5)

* Prepare Community React and Pro access CLI packages

* Rename npm packages to unscoped ThreeUI names

* Publish ThreeUI packages under DesignCode scope

* Automate Community package releases

* Follow renamed Community component sources

* Exclude Beta renderer imports from Community sync

* Sanitize renamed Community section assets

* Normalize synced renderer module paths

* Resolve canonical source paths during sync

* Preserve public adapters across catalog sync

* Copy only active Community runtime assets

* Use current GitHub Actions runtimes