Publish embedded package for releases of Element Call (#3086)

* Publish embedded package for releases of Element Call

Part of https://github.com/element-hq/element-call/issues/2994

This PR:

- Publishes embedded builds as Tarball, NPM, AAR, SwiftPM for releases
- Publishes full builds as Tarball for releases
- Adds comments to release notes with the built artifact locations

* Update embedded/web/package.json

Co-authored-by: Michael Telatynski <7t3chguy@gmail.com>

* Update .github/workflows/publish-embedded-packages.yaml

* Update embedded/ios/Package.swift

* Apply suggestions from code review

* Try dry-run of gradlew

* Whitespace

* Fix more instances of unpinned GHA

* Minimise permissions

* Upload release notes once

To reduce concurrency

* Fix npm publish permissions

---------

Co-authored-by: Michael Telatynski <7t3chguy@gmail.com>

README.md

@@ -52,10 +52,12 @@ Element Call can be packaged in two ways:
 **Full Package** – Supports both **Standalone** and **Widget** mode. Hosted as
 a static web page and accessed via a URL when used as a widget.
 
-**Embedded Package** – 🚧 **Coming [Soon](https://github.com/element-hq/element-call/issues/2994):** Designed for **Widget mode** only. Bundled with a
+**Embedded Package** – Designed for **Widget mode** only. Bundled with a
 messenger app for seamless integration. This is the recommended method for
 embedding Element Call into a messenger app.
 
+See the [here](./docs/embedded-standalone.md) for more information on the packages.
+
 ### Standalone mode
 
 ![Element Call in Standalone Mode](./docs/element_call_standalone.drawio.png)