Added project management commands

[e4coder]

Changelog / Overview

• manim init - quickly sets up default files for a manim project.
• manim new project - lets the user set project settings. It also creates the project inside a new folder of name <project_name>
• manim new scene - used to quickly insert new scenes into files. If file name is not provided main.py is used as default.

Added 3 commands in the "manim/cli/project/commands.py" file. Added 2 tests in "tests/test_commands.py"

Update:

directories have been restructured.
init command resides in manim/cli/init/command.py.
new command group resides in manim/cli/init/group.py

I also have changed the name of manim/cli/cfg/commands.py to manim/cli/cfg/group.py

Motivation

I want new users to quickly be able to create example scenes and edit those scenes to their liking. Some of my friends don't want to use manim only because they found it very hard

Explanation for Changes

New users of manim will be able to quickly set up projects and scenes from templates. The number of templates is very few at the moment but we can add more.

Commands

1 - manim init : this command quickly sets up default files for a manim project

manim init

2 - manim new project : this command lets the user set project settings. it also creates the project inside a new folder of name <project_name>. this command can be used in 3 different ways

manim new project
manim new project <project_name>

3 - manim new scene : this command is used for inserting new scenes in files. if file name is not provided main.py is used as default. if file name is provided but file name does not exist. new file is created with name file name

manim new scene <scene name>
manim new scene <scene name> <file name>

Testing Status

My PC specs:
Processor:............. core I 5 2400
RAM:..................... 8 GB ddr3 ram
GPU:..................... AMD rx 470
Operating System: Ubuntu 20.04

I have tested these commands extensively in ubuntu. I have not tested them in Windows. however i believe they will work fine

Further Comments

Checklist

• I have read the Contributing Guidelines
• I have written a descriptive PR title (see top of PR template for examples)
• I have written a changelog entry for the PR or deem it unnecessary
• My new functions/classes either have a docstring or are private
• My new functions/classes have tests added and (optional) examples in the docs
• My new documentation builds, looks correctly formatted, and adds no additional build warnings

Reviewer Checklist

• The PR title is descriptive enough
• The PR is labeled correctly
• The changelog entry is completed if necessary
• Newly added functions/classes either have a docstring or are private
• Newly added functions/classes have tests added and (optional) examples in the docs
• Newly added documentation builds, looks correctly formatted, and adds no additional build warnings

[e4coder]

checks are failing for template scenes.

[e4coder]

I think I touched everything mentioned in the comments. let me know if I missed anything. thx

[jsonvillanueva]

I think these are the last tidbits for making the CLI display help pages properly. Other than this, I think the subcommands work as intended. It may be worth adding documentation for these subcommands somewhere in the tutorials section, but I think this can be done in a future PR.

[e4coder]

@kilacoda Sir it's been 4 days since you requested changes. could you possibly review them? thx

[kilacoda-old]

Sorry, got caught up in some other stuff! Reviewing rn.

[kilacoda-old]

LGTM!