i15-1: Logged-in / logged-out states and Dashboard content

We need to define what users should see depending on whether they are logged in or logged out.

### Logged-out state

Currently, logged-out users may be able to see pages that should perhaps only be available after logging in.

We should decide what the logged-out experience should include. For example:

* An About page
* A clear log-in call to action
* Limited navigation, rather than showing all application pages

(Similar to ULIMS)

### Logged-in Dashboard

We also need to decide what information should appear on the Dashboard once a user is logged in.

The Dashboard is not intended to show only the user's own logged in state. Instead, it should provide a useful overview of relevant information from across the application, for example:

* A mini queue
* Selected camera views
* Other key information or status summaries from different areas

### Decisions needed

* What pages/content should be accessible when logged out?
* What should the logged-out landing page look like?
* What information should be surfaced on the logged-in Dashboard?

Start by reviewing the current application pages, authentication states, and Dashboard entry point to inventory what logged-out and logged-in users can see. Compare the intended logged-out experience with ULIMS, then define the accessible pages, landing content, and Dashboard information that satisfy the issue's decisions.

Written by the indexing model from the issue text.