v4.4.7 - Self-heal frontend runtime on cms upgrades

Bug Fixes

Two issues caused the frontend runtime (public/vendor/tallcms/tallcms.js) to drift out of sync with the package on existing hosts. After v4.4.7 they self-heal on every composer update.

• Auto-publish on composer update: The cms package's compiled assets are now also registered under Laravel's conventional laravel-assets publish tag. The standalone scaffold's standard post-update-cmd hook runs vendor:publish --tag=laravel-assets --force on every composer update, so any cms upgrade that ships a new tallcms.js / tallcms.css automatically refreshes public/vendor/tallcms/. Previously the package only registered tallcms-assets, which had to be invoked manually.
• Cache-bust the runtime URL: @tallcmsCoreJs now appends the published bundle's mtime as a ?v= query string. Browsers automatically pick up the new bundle on the next request after a cms upgrade — no more "I republished but the form still fails because my browser had the old JS cached."

Why it matters

The _page_url → _pageUrl rename in the contact-form runtime broke contact submissions on hosts whose public/vendor/tallcms/tallcms.js hadn't been republished, even though Composer pulled the new dist into vendor/. Both fixes together mean the next runtime contract change of this kind propagates without manual ops steps.