[SYNPY-1571] Adds Dataset Model & Introduces Composition Model for Table/View-like Classes

[BWMac]

Problem:

We do not currently have an OOP Class representing the Synapse API Dataset Model. Additionally, the nature of the Synapse API Models for Table-like objects is such that our previous approach of Table classes being simply extended to include the functionality that is expected of View-like objects did not work well in practice.

Solution:

This PR finishes the Dataset OOP model class. While implementing the methods for this class, we needed to add functionality to handle the default columns that Dataset and EntityView objects have when represented as a Table on Synapse. Logic within the AsynchronousCommunicator class was also updated to handle asynchronous jobs in the Synapse backend failing gracefully. All necessary documentation for the Dataset model was added.

This PR also introduces a composition-based approach to creating all Table-like classes by splitting up the major pieces of Table and View functionality into individual Mixin classes. These Mixins can then be used along with previously implemented Mixins (i.e. AsynchronousCommunicator and AccessControllable) to create our final OOP models for Table, Dataset, EntityView, etc. with minimal code and test duplication. The logic that was previously apart of TableOperator has been redistributed into these Mixins. One strength of this approach is that the Mixins can be unit tested once and then the classes that inherit them only need to be tested for their unique methods.

Testing:

All needed unit and integration tests were added/updated. All of the functionality included with the Dataset class (synchronous interface) can be tested by running the included demo script.

Notes:

I went ahead and bumped up all usage of ubuntu-20.04 to ubuntu-22.04 before that GH runner reaches EOL on April 1st.

[BryanFauble]

This is some seriously great work here! Thanks so much for your attention to these changes.

I know we're still working to resolve the integration test issues, but the bulk of all the changes here are good to go. I also know there are a few items that I've fixed in #1181 that will be merged into develop after this PR.