feat: update codebase to reflect the latest configuration in the parent open-sdg and open-sdg-site project

[jaylenw]

What does this PR do?

• Add GitHub Issue & PR Templates
• Update configuration files to reflect the needs of the project and that were provided in https://github.com/open-sdg/open-sdg/releases/tag/2.3.0 and https://github.com/open-sdg/open-sdg-site-starter/tree/256f6db3daeed1ae5c250be5d7fe84694cdb3132/
• Update GitHub Action workflow files to support build, verification, and deployment.

Background info

• GitHub Actions workflows are failing as seen here https://github.com/CityOfLosAngeles/open-sdg-site-starter/actions/runs/8253771317 due do the build process accessing the outdated version of the data site. The workflows should be able to complete successfully after the latest data build configuration has been deployed and changes are made to the site that resolves the errors from running the HTML validation scripts.

• @kerrylacity @naomiikd I think you two should create a GitHub Issue to resolve the errors below that occurs when ./scripts/test/html_proofer_staging.sh and ./scripts/test/html_proofer_prod.sh are ran once this PR has been merged.

vscode ➜ /workspaces/open-sdg-site-starter (ghi-25) $ ./scripts/test/html_proofer_staging.sh 
Running ["ScriptCheck", "LinkCheck", "ImageCheck"] on ["./_test"] on *.html... 


Ran on 561 files!


- ./_test/index.html
  *  internally linking to ../goals, which does not exist (line 257)
     <a href="../goals">goal</a>

HTML-Proofer found 1 failure!
vscode ➜ /workspaces/open-sdg-site-starter (ghi-25) $ ./scripts/test/html_proofer_prod.sh 
Running ["ScriptCheck", "LinkCheck", "ImageCheck"] on ["./_site"] on *.html... 


Ran on 561 files!


- ./_site/index.html
  *  internally linking to ../goals, which does not exist (line 257)
     <a href="../goals">goal</a>

HTML-Proofer found 1 failure!
vscode ➜ /workspaces/open-sdg-site-starter (ghi-25) $ 

• Certain files within the _layouts directory has been updated by referring to https://github.com/open-sdg/open-sdg/tree/2.4.0-dev/_layouts. The changes were updated to have the build process complete successfully.

SDG Data Portal accessible via localhost:9000 after following the README.md's instructions

Running Jekyll Server to serve built site locally

*Note that not all of the data will load on the site as there is a CORS issue present. This should not exist with configuration in the cloud environment.

How can this be tested (manually and/or automated test)?

Provide manual tests steps if applicable

The README.md mentions accessing the site locally in the browser by running the jekyll serve command. Refer to the instructions to be able to manually browse the site.

Provide steps for running automated tests if applicable

Please refer to the documentation in the README.md for testing locally.

Which issue(s) is/are related to this PR?

This PR is/are related to issue(s) #25

close #25

[jaylenw]

@naomiikd @kerrylacity , as part of the review process please verify the steps for running the site locally works for you.