As a staff user, I want to see when someone last logged in for a specific business so when someone calls I have that information to explain why they were dissolved.

### Staff see who last
## Description:
Given a staff is signed in
And the user is on the entity dashboard
Then the staff user should be able to see when a public user last was in the entity dashboard

**Dependencies**

**Acceptance Criteria**

**Validation Rules**

Ready to Build (DoR):
- [ ] Stakeholders have approved
- [ ] User story completed (full flow of business rules, happy and alternate paths etc.)
- [ ] What are the dependencies
- [ ] Validation rules defined (UI, Data, Role-Action)
- [ ] Is a formal UAT required
- [ ] Acceptance Criteria well defined in tickets (Story level) QA can confirm or deny
- [ ] Reference BA checklist for this story (functional description captured ?)

Acceptance / DoD:
- [ ] PR to remove feature flags created
- [ ] Check Requirements against completed stories
- [ ] Completed stories verified in Dev/Test/Prod
- [ ] Confirm Test cases built and succeeding
- [ ] Confirm successful End-End runs
- [ ] No regression
- [ ] All Linters passed
- [ ] Test coverage and Test ID acceptable by Product owner
- [ ] Ticket merged to master or story branch
- [ ] Add / maintain selectors for QA purposes
- [ ] Add PR numbers - If available
- [ ] All tests passed (Jest, Pytest, Postman)
- [ ] Developer to list Config changes/ Update documents and designs
- [ ] Design / Solution accepted by Product Owner
- [ ] Acceptance criteria has been defined (happy path, known sad paths)
- [ ] Test coverage acceptable
- [ ] Peer Reviewed
- [ ] Accessibility reviewed and acceptable [checklist](https://github.com/bcgov/entity/docs/coding-standards/accessibility.md)
- [ ] UX Approved
- [ ] PR Accepted
- [ ] Production burn in completed

Start by reviewing the entity dashboard entry point and clarifying the missing dependencies, validation rules, roles, and acceptance criteria. Trace where dashboard activity data is currently presented, then define the relevant test cases and confirm that the last-login information is visible to staff and covered by the documented definition of done.

Written by the indexing model from the issue text.