Easily install missing IronPython extension package

[aparajit-pratap]

Purpose

Easily install missing IronPython extension package.

Declarations

Check these if you believe they are true

• The codebase is in a better state after this PR
• Is documented according to the standards
• The level of testing this PR includes is appropriate
• User facing strings, if any, are extracted into *.resx files
• All tests pass using the self-service CI.
• Snapshot of UI changes, if any.
• Changes to the API follow Semantic Versioning and are documented in the API Changes document.

Reviewers

@DynamoDS/dynamo

FYIs

(FILL ME IN, Optional) Names of anyone else you wish to be notified of

[mmisol]

Some questions related to this PR and the future. Probably something we should answer as a team.

What should be the strategy for releasing future versions of the Iron Python engine package? Should 2.7.9 be the version here and whenever 3.0.0 is released we deprecate the previous version of the package in PM (if that's possible)?

We talked about removing the migration functionality in Python Epic 8. I think we should make sure to do that at a time it is no longer relevant, which would have to be some time after we deprecate the 2.7.9 version of the Iron Python engine package. I'm not sure if it should be enough to infer some info about usage from Package Manager, by tracking downloads, or if we should use analytics to cover cases where users have already installed the package and are just using it.

[aparajit-pratap]

These will be updated once the IronPython extension is published to PM prod.

[aparajit-pratap]

What should be the strategy for releasing future versions of the Iron Python engine package? Should 2.7.9 be the version here and whenever 3.0.0 is released we deprecate the previous version of the package in PM (if that's possible)?

@mmisol, as discussed I think the strategy is to add new packages for new engine versions and make them available in the PM in the future.