✨ Move PROS 4 to early access

[12944qwerty]

Summary:

Deprecate PROS v3.

• Renames beta to modern or v4
• warns user v3 is deprecated once

Closes #295

[ayushuk]

For CLI changes, we usually required you to test your changes with a test plan expected and actual outputs on the PR. Overall it looks good, good job.

[ayushuk]

Closes #295

[ayushuk]

Create new pros 3 project without early access flag for the first time:

Create a new pros 3 project after the first time without the flag:

Create a new pros 4 project with the early access flag:

Create a new pros project after early access is enabled:

resolved

[noam987]

Only concern I have is the okapi Message (also We should move okapi out of being a default template)

[ayushuk]

Need to fix the okapi error

[ayushuk]

There are some issues I have with the current flow.

1. Saying "no" to the initial prompt that says "PROS 3 is available" just raises an error and ends the execution. When you try to create a new project the directory is already created so then you try to make a project again and it gives you an error that a project already exists even though its just a directory with project.pros so then you have the delete that directory to make a project. When you make a new project after deleting the directory it makes a project in PROS 3 after the user already said no to using PROS 3. Seeing an error after saying no is probably just going to cause confusion and I think when someone says no to the prompt a PROS 4 project should just be created.
2. There isn't any way (other than deleting conductor.pros) to turn off early access after you already enabled it. For someone that accidentally enabled early access we should have a way for them to turn off early access. This can probably be a flag. We dont want people going through hoops to reverse an action they accidentally did.
3. I tried to make a PROS 3 project with early access enabled and I got an error where it tried to apply LVGL. The LVGL template shouldn't be trying to be applied to PROS 3. We should fix this to avoid confusion.

[ayushuk]

Code lgtm, will test this out tomorrow I think we should be good to merge

[ayushuk]

imo --disable-early-access > --no-early-access but open to more opinions

[ayushuk]

Some things after testing this.

1. The disable early access feature works very well for me, tried some edge cases and it performs as I expect
2. The problem I mentioned in point 1 of the large comment above about raising an error and creating a directory is still partially an issue. When you choose "no", an empty project directory is created, while you can make a new project with the same name, its still an issue to be because the directory still exists. For this reason, I think when someone selects the "no" option to "do you want to use pros 3" then you should just go ahead and make a PROS 4 project instead of having to run another command since we already know their intention.
3. Point 3 in the large comment is still an issue

[ayushuk]

LGTM