Add control over root URL behavior

[joshavant]

Is your proposal related to a problem?

Currently, the root URL of a deployment (e.g. the value for NEXT_PUBLIC_WEBAPP_URL) redirects to /auth/login.

For self-hosters, this may not be a desired behavior.

For example, I'm interested in self-hosting a Cal.com deployment for my own, personal schedule. For my usecase, I definitely don't want NEXT_PUBLIC_WEBAPP_URL to present a login screen, because that URL is easily guessable by the public (e.g. if I promote https://schedule.josh.com/josh people will probably try accessing https://schedule.josh.com).

It would be nice to have a first class feature to allow control over this behavior.

Describe the solution you'd like

Some desired control functionality would be:

1. Allow me to redirect this URL to a specific user's page (e.g. from the example above https://schedule.josh.com > https://schedule.josh.com/josh) (easy, less preferable, straightforward with current architecture)
2. Allow me to show a specific user's page (e.g. https://schedule.josh.com shows the content of https://schedule.josh.com/josh) (harder, most preferable, not straightforward with current architecture?)

Describe alternatives you've considered

Editing source code to do Proposed Solution 1.