chore(seed): freeCodeCampify challenges: 00, 01, 02)

[no-stack-dub-sack]

Pre-Submission Checklist

• Your pull request targets the staging branch of freeCodeCamp.
• This PR targets feature/curriculum-expansion
• Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
• You have only one commit (if not, squash them into one commit).
• All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

• Small bug fix (non-breaking change which fixes an issue)

Checklist:

• Tested changes locally.

Description

• Partial completion of issue Change name from "Free Code Camp" to freeCodeCamp everywhere #12472 - for replacing all instances of "Free Code Camp", "freecodecamp", etc. with "freeCodeCamp" within the codebase.
• Since the staging brach will be merged/replaced with curriculum expansion anyway, I was advised to perform these updates directly on the feature/curriculum-expansion branch
• This PR targets instances within the freeCodeCamp/seed/challenges directory. Specifically:
  • 00-getting-started
  • 01-responsive-web-design
  • 02-javascript-algorithms-and-data-structures
• Where challenge seed or tests was concerned, I replicated the challenges locally to make sure nothing was affected.

Unfortunately, I don't think there is any way to avoid the QA process for these being a nightmare, but for whoever is QAing, let me know if I should go for smaller chunks next time.

[raisedadead]

@no-stack-dub-sack

Closing this as discussed, and we can take this on top of #12570 after it has been merged? Thanks a lot. You should wait for staging in that case.

[no-stack-dub-sack]

@raisedadead Yup, that works. No prob, worth doing it over again to have all the new challenges in staging!

[raisedadead]

Thanks for all the hard work! 😉