Feature Initialization requires authenticated user with an "exp" claim.

We recently implemented Elsa Studio with Auth0 authenticated backed by SSO (Azure Entra). This results in an Identity that does not have an "exp" claim as it doesn't expire. It hasn't been a big headache as Features don't really seem to require being Initialized. The only exception in the standard set seems to be if you are adding something to the top app bar. Just curious if this is completely intentional?

https://github.com/elsa-workflows/elsa-studio/blob/1d526cfc66c35dd5b1ca7272147240d0be8bbb4d/src/framework/Elsa.Studio.Shared/Layouts/MainLayout.razor.cs#L46

Start in src/framework/Elsa.Studio.Shared/Layouts/MainLayout.razor.cs at line 46 and inspect why feature initialization depends on an authenticated user's "exp" claim. Trace the top app bar feature path and compare it with other standard features. Done means the intended behavior for identities without an expiration claim is established and the affected initialization path handles it consistently.

Written by the indexing model from the issue text.