Implement the 11.0.3-to-11.1.0 migration notebook

[eecavanna]

In this branch, I created a new migration notebook. This one can be used to migrate the Mongo database from conforming to schema version 11.0.3 to conforming to schema version 11.1.0.

There is a caveat, though: Since the new schema hasn't been released yet, I don't know what its version number will actually be. I have assumed it will be 11.1.0, but that may not be what it ends up being—in which case, I'll update this branch.

Details

I also moved some notes from the notebook to the example config file. Finally, I changed the import section so that the migrator gets imported based upon a string variable. That will make it easier for us to transition from using a notebook to using a regular Python script (we can pass the string in as a CLI argument).

Related issue(s)

Fixes #760

Related subsystem(s)

• Runtime API (except the Minter)
• Minter
• Dagster
• Project documentation (in the docs directory)
• MongoDB migrations
• Other

Testing

• I tested these changes (explain below)
• I have not tested these changes yet

I tested the notebook locally against a copy of production data.

Documentation

• I have not checked for relevant documentation yet (e.g. in the docs directory)
• I have updated all relevant documentation so it will remain accurate
• Other (explain below)

Maintainability

• Every Python function I defined includes a docstring (test functions are exempt from this)
• Every Python function parameter I introduced includes a type hint (e.g. study_id: str)
• All "to do" or "fix me" Python comments I added begin with either # TODO or # FIXME
• I used black to format all the Python files I created/modified
• The PR title is in the imperative mood (e.g. "Do X") and not the declarative mood (e.g. "Does X" or "Did X")

[eecavanna]

I'm merging the migration notebook in without additional review (as usual).