Draft a CEP for `conda` Plugins Standards and Best Practices

[beeankha]

With all of the upcoming plugins work and the possibilities related to them, it would be beneficial to come up with a core set of standards and best practices that have been discussed and agreed upon.

Possible topics to discuss include:

• Versioning
• Terminology
• Tests
• Verbosity / debug output
• Output format
• Preserving certain conda CLI arguments (e.g., -n, -p, -c, etc.)

Note: Standards that would only apply to certain plugins (e.g., a solver or authentication plugin) may be discussed within a separate CEP for those particular plugins.

[AlbertDeFusco]

One thing I've been thinking about is that it may be considered best practice to not change important conda CLI arguments like -n, -p. and potentially others. That's not to say that all plugins have to work with named envs and conda env prefixes, but it would be best if plugins did not implement those flags that then change their meaning, which would lead to user confusion.

[beeankha]

Thank you for those details, @AlbertDeFusco! I'll be sure to include that in the upcoming CEP; I also updated the list above in the issue description. 👍