try2:Fixed all the old style Free Code Camp to freeCodeCamp in seed/challenges

[Dazler]

Pre-Submission Checklist

• Your pull request targets the staging branch of freeCodeCamp.
• 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)
• New feature (non-breaking change which adds new functionality)
• Breaking change (fix or feature that would change existing functionality)
• Add new translation (feature adding new translations)

Checklist:

• Tested changes locally.
• Closes currently open issue (replace XXXX with an issue no): Closes #XXXX

Description

[dhcodes]

@Dazler you'll need to rebase your branch with git pull --rebase upstream staging and then push this branch again with -f to get rid of the merge conflicts. Also, in the future, please name your branch something like fix/change-freecodecamp-style.

[raisedadead]

Refers #12472

[raisedadead]

@Dazler Hi Avinash, we are closing this, please do not be disheartened, I know this is your first time contributing, and you are doing a good job, but I suggest that you start with a simpler, smaller issue.

This one is a bit complicated, with need for rebasing, merging every now and then as the seed code is being worked upon very frequently.

I think you should do a smaller change that gives you a good idea of the process.

Please reach out to us in the Contributors Chat room, we are super excited to help you!

Thanks a lot and happy fixing!