PRD - Update all agendas to include pre-meeting checklist for leads

### Overview
We need to add pre-meeting work checklists to agendas so that we effectively communicate lead responsibilities and provide them with a means of completing that work, ensuring that the project board stays properly maintained.

### Action Items

- [ ] For each agenda (PM, Dev, UX, General)...
- [ ] Add a section for accountability checks, provide example link that demonstrates how to see all tickets currently assigned to a volunteer
- [ ] In resources, Include a copy/paste section for the recommended saved reply for accountability checks
- [ ] Add instructions for how to get in touch with volunteers who have missed an update
- [ ] add `needs update` label
- [ ] reach out on slack using the same accountability check saved reply, comment with the slack link to this message
- [ ] add instructions to begin offboarding after 2 missed updates, provide a link to the appropriate channel they should reach out to if they want to re-onboard
- [ ] Add a checklist item that allows lead to review tickets that need their attention
- [ ] provide link to this role's project board
- [ ] provide link to this lead's `ready for` board
- [ ] Add sub-item to review Icebox
- [ ] Add sub-item to review Questions
- [ ] Add sub-item to review In Review

#### Ticket Bookkeeping
- https://github.com/hackforla/311-data/issues/1494
- [ ] remove the dependency label
- [ ] move the ticket to New Issue Approval
- [ ] add "ready for design lead" label

### Resources/Instructions
#### Bonnie's Instructions on how to structure the "To Update" labels
- https://github.com/hackforla/product-management/issues/386#issuecomment-2867658845

#### Saved Reply With Instructions for Accountability Checks

Click to see Accountability Check saved reply

```
@

Hi , please provide the items requested below. If you have questions, click the Instructions dropdown for more info. Thanks!

Instructions

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (if necessary): "Add any pictures that will help illustrate what you are working on."

1. Progress:
2. Blockers:
3. Availability:
4. ETA:
5. Pictures (if necessary):
```

Product Team's Pre-Work Checklist

```
- [ ] All issues in New Issue Review/Approval have either:
- [ ] The `ready for...` label: [Project Board: Missing Ready for Labels](https://github.com/orgs/hackforla/projects/63/views/22)
- If this link shows any issues in New Issue Approval, they need to be given the appropriate "ready for..." label
- [ ] The `draft` label and assignee
- [ ] All issues in Questions column have a `ready for...` label [Project Board: Missing Ready for Labels](https://github.com/orgs/hackforla/projects/63/views/22)
- If this link contains any issues in Questions, they need to be given the appropriate `ready for...` label.
- [ ] All issues in Review column have a `ready for...` label [Project Board: Missing Ready for Labels](https://github.com/orgs/hackforla/projects/63/views/22)
- If this link contains any issues in Review, they need to be given the appropriate `ready for...` label.
- [ ] Review the issues on [Project Board: Ready for Product](https://github.com/orgs/hackforla/projects/63/views/19)
- [ ] address them now or add to this agenda to discuss.
- [ ] For each issue in Questions that has `on agenda:` label, add a link to the question-asking comment from each new issue to the the agenda below
```