Refactor current-projects-check file to fix any formatting issue with new tools data format

[ronaldpaek]

Overview

The purpose of this issue is to refactor the code in the current-project-check file to handle a list of strings(tools), instead of a single one. This change will maintain consistent formatting and resolve problems introduced by the recent change in data format.

Action Items

• Refer to current-projects-check.js and locate where tools is being referenced
• Refactor this code so tools can work as a comma separated String or an Array

{%- if project.tools -%},
"tools": `{{ project.tools }}`
{%- endif -%}

to:

{%- if project.tools -%},
"tools": {{ project.tools | jsonify }}
{%- endif -%}

• Refactor this code to map over tools since tools will be an Array now and not a String

${project.tools ?
`
<div class="project-tools">
<strong>Tools: </strong>
${ project.tools }
</div>
`:""
}

to:

${project.tools ?
`
<div class="project-tools">
<strong>Tools: </strong>
${(Array.isArray(project.tools) ? project.tools : project.tools.split(','))
    .map(tool => `<p class='project-card-field-inline'> ${tool}</p>`)
    .join(", ")
}
</div>
`: ""
}

• After completing both changes this should allow us to make changes to tools without effecting the functionality of the website

Merge team:

• Once this issue is merged, release its dependency in Create new issues to refactor Tools data in project md files  #4777

Resources/Instructions

• Projects page
• Liquid template language
• This issue is part of an epic: Add a Tools filter to the projects check page #4427