Release v4.152.0

Commands that rendered applications and the live Stage send now go through Arc's generated command proxies, so they keep the application's API base path, microservice and identity headers.

Changed

• The Stage runtime executes every command through the registered Arc command proxy, configured like useCommand, instead of its own fetch. Arc now checks required command properties in the browser before the call, the same rule the server enforces. (part of #499)
• The live Stage's /stage/routes also returns each command's JSON schema, keyed by the command's full name, so the Stage can build a proxy for every command, including commands with the same name in different modules. (part of #499)

Fixed

• Commands sent from a rendered application lost the API base path, the microservice and the identity headers that Arc adds, so they could reach the wrong route or arrive unauthenticated. (part of #499)