[Enhancement - ADMIN] Login screen [April]

#### Description:
This ticket is to update Admin login to reflect design standards.

Notes:
- side panel should not be visible if a user is not logged in.

#### User Story:
As an Admin, I want to be able to login to the reservations Day Use Pass system via my IDIR so that I can easily manage DUP offerings.

As a park operator, I want to be able to login to the reservations Day Use Pass system via my BCSC or BCeID account so that I can check-in passes and complete other administrative tasks as needed.

#### Acceptance Criteria:

Given I am a government staff (Admin) user
When I go to log into the Admin system
Then I can do so with my government IDIR

Given I am an Park Operator
When I go to log into the Admin system
Then I can do so with my personal BC Services Card

Given I am an Park Operator
When I go to log into the Admin system
Then I can do so with my BCeID account

#### Development Checklist:

- [ ] Add "Log in with BC Services Card" Button and info link. Ensuring functionality of BCSC log in flow.
- [ ] Add "Log in with BCeID" Button and info link. Ensuring functionality of BCeID log in flow.
- [ ] Update with any more information after meeting with BCeID team Wednesday Feb 4th.
- [ ] Add "Log in with IDIR" Button. Ensuring functionality of IDIR log in flow.

#### Dependencies
- Meredith to add BCeID to Login page: https://github.com/bcgov/reserve-rec-admin/issues/135

**Wireframe(s):**
- [Figma, dev ready login design](https://www.figma.com/design/7ZxtMEp3I425MXcechDB2J/PRDT---Admin?node-id=3620-12622&p=f&t=roNcA38cPqtyS1SO-0)

**Workflows:**

#### Documentation:
- [Day Use Pass Admin requirements - Confluence](https://apps.nrs.gov.bc.ca/int/confluence/pages/viewpage.action?pageId=275678059)

#### Notes:
-
-

**Definition of Ready** (Note: If any of these points are not applicable, mark N/A)

- [ ] User story is included
- [ ] User role and type are identified
- [ ] Acceptance criteria are included
- [ ] Wireframes are included
- [ ] Design / Solution is accepted by Product Owner
- [ ] Dependencies are identified (technical, business, regulatory/policy)
- [ ] Story has been estimated (under 13 pts)

**Definition of Done**
- In progress:
- [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
- [ ] UI meets accessibility requirements
- [ ] Unit tests are written
- [ ] Work is traceable in GitHub
- [ ] PR linked to ticket number
- [ ] If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment

- Code review:
- [ ] Code is peer reviewed and has passed CI/CD tests

- QA:
- [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
- [ ] Code is potentially shippable to the production environment
- [ ] Functional features have been tested and passed by QA
- [ ] UI components tested by designer
- [ ] Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)

- PO Review:
- [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
- [ ] Reviewed and approved by Product Owner

Start with the linked Figma login design and the Day Use Pass Admin requirements in Confluence, then review dependency issue #135 about adding BCeID. Confirm the required IDIR, BC Services Card, and BCeID flows with the relevant teams before locating the Admin login entry point. Done means all three login options work, the unauthenticated side panel is hidden, and the acceptance criteria, accessibility, unit tests, and QA checks pass.

Written by the indexing model from the issue text.