Add Configurable Default Origin URL for Serverless Functions

[robertocommit]

Is your feature request related to a problem? Please describe. When deploying applications with serverless functions on Stormkit, the default origin is set to localhost with a port. This creates challenges when configuring CORS in backend applications, as the port makes it difficult to maintain consistent CORS settings. Currently, there's no way to set or view a fixed origin URL for serverless functions unless using specific framework logic.

Describe the solution you'd like

1. Add a dedicated section in the serverless configuration UI that displays a default origin URL for serverless functions
2. Optional: allow users to view and modify this origin URL through the Stormkit dashboard
3. Automatically apply this origin URL when deploying serverless functions instead of using localhost

Additional context This feature would improve the developer experience by:

• Simplifying CORS configuration for serverless functions
• Reducing potential security risks from overly permissive CORS settings
• Making it easier to maintain consistent development and production environments
• Following standard practices for serverless function deployment

[svedova]

Thanks for opening this issue! I have implemented the following behaviour:

• If the ORIGIN environment is provided by the user, it will be used.
• If it's not provided, Stormkit will inject the hostname as the ORIGIN environment variable.

It's already in latest branch, and it will be included in the upcoming release so closing this issue 🙏