Create new issues to refactor Tools data in project md files

[t-will-gillis]

Dependency

• Identify which pages call Tools data from each project #4525
• Create new issues to refactor each page & files using Tools data #4776
• Refactor project page to fix any formatting issues with new tools data format #4859
• Refactor current-projects file to fix any formatting issue with new tools data format #4860
• Refactor current-projects-check file to fix any formatting issue with new tools data format #4861

Overview

As part of the sequence of steps to revise the filters to include a dropdown menu for Tools (issue #4427), once the above dependencies are released, we need to create new issues for editing each of the following project .md files in the _projects folder: when the above dependencies are released, move each issue below from the "Ice Box" to "New Issue Approval", remove the Dependency label and add Ready for prioritization label.

• Refactor Tools data for access-the-data.md #4798
• Refactor Tools data for brigade-organizers-playbook.md #4799
• Refactor Tools data for civic-tech-index.md #4800
• Refactor Tools data for civic-tech-structure.md #4801
• Refactor Tools data for design-systems.md #4802
• Refactor Tools data for ems-triage-tracker.md #4803
• Refactor Tools data for engage.md #4804
• Refactor Tools data for food-oasis.md #4805
• Refactor Tools data for green-earth-os.md #4806
• Refactor Tools data for hellogov.md #4807
• Refactor Tools data for home-unite-us.md #4808
• Refactor Tools data for lucky-parking.md #4809
• Refactor Tools data for metro-ontime.md #4810
• Refactor Tools data for open-community-survey.md #4811
• Refactor Tools data for public-tree-map.md #4812
• Refactor Tools data for website.md #4813
• Refactor Tools data for youthjusticenav.md #4814
• Refactor Tools data for tech-work-experience.md #4913

Action Items

• For each of the above issues, click on the target icon that appears to the far right when hovering on the line to "Convert to issue".
• Edit the issue title by prepending Refactor Tools data for in front of current issue title. For example:
  • if the new issue created is called access-the-data.md then
  • the new issue title will be Refactor Tools data for access-the-data.md
• Add the labels role: front end, role: back end/devOps, good first issue, size: 0.5pt, P-Feature: Project Info and Page, P-Feature: Projects page, p-feature: Projects-check
• Add to the Projects Board in the "Ice Box"
• Add the milestone 03.02 Onboarding flow <<Confirm
• Use the template below in the body of the new issue. Be sure to replace "PROJECT_NAME" with the correct md file name, and replace "<SHOW_3_BACKTICKS>" with 3 backticks.

### Dependency

- [4777]

### Overview

We need to revise the filter dropdown menu on the [projects-check] page to include a dropdown for Tools, so that we can use this page to see where we might need to move projects values from tools to technologies, and vice versa. In order for the filter to work properly, we need to refactor the `tools` data in the .md file from a string to a list.

### Action Items

- [ ] Refer to the [PROJECT_NAME.md](https://github.com/hackforla/website/blob/gh-pages/_projects/PROJECT_NAME.md) file and find the entry for `tools:`
- [ ] Change the `tools` data from a string into a list: 

`tools: tool_1, tool_2, tool_3`  becomes:
<SHOW_3_BACKTICKS>
tools: 
  - tool_1
  - tool_2
  - tool_3
<SHOW_3_BACKTICKS>
- [ ]  

### Resources/Instructions

- [Homepage](https://www.hackforla.org)
- [Projects](https://www.hackforla.org/projects/) page
- This issue is part of an epic: #4777

For Merge Team/Tech Leads/PMs

• Once the PRs for all of the above issues are closed, remove the dependency for this issue on Add a Tools filter to the projects check page #4427

Resources/Instructions

• Homepage
• Projects page