Adds basic outline for Python challenges.

[cldershem]

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

Addresses #14588 per discussion with @raisedadead and @Ethan-Arrowood . This is a basic outline of a way the Python curriculum can be organized. We are currently decided on an actual implementation pending a few related issues. However, this will get the ball rolling forward and we can script or manually update all of the challenges at a later date when we have figured out a solution for FCC integration.

The lessons contained in the original issue thread and future challenges should be submitted against this branch directly. Anything currently in this is here only as a placeholder to get things started.

[QuincyLarson]

Thanks for your pull request, @cldershem. Our plan is to incorporate these challenges into a stand-alone app first. So I'm closing this pull request for now.

[cldershem]

@QuincyLarson Thanks for the heads up. I had originally tried to do this as a separate repo, but was informed this would be a better way to do it. Is it possible to get a FCC-Python repo under the 'freeCodeCamp' org? Or when you say standalone app, do you mean incorporating things directly into 'repl.it' first? If so, my idea behind the repo was to make contributions easier and to keep things organized and in version control.