Allows users to A/B test the new parse-tree work

[schuylermartin45]

• Adds some new functionality to the Recipe class so that callers can utilize some of the newest features of the parse-tree effort.
• These changes are intended to ensure backwards compatibility and reduce the "blast radius" to zero or near zero. Current code in operation will not be opted-in to these changes. A user must explicitly opt-in.

Manual testing with the recipe command was performed to ensure the CLI works as expected with the new --parse_tree flag.

I argue that once this is in, we should bump percy to the next version so AnacondaLinter can start using the parse tree work.

[schuylermartin45]

@cbouss I double checked and I believe all of those concerns are captured in the JIRA Epic.

If you're concerned about breaking the linter, I wonder if we could de-escalate some auto-fixes that are more experimental/use this newer work. In other words, if some fixes fail, don't flag them as critical and revert their automatic changes?

Alternatively, we put in the effort to build-out some integration testing layer in the linter's pipeline. That's just more work, but we should probably do it at some point. Arguably we should have a development stage as well for the linter. Of course, if that's what you mean by beta then I think we're on the same page :)