Render OpenAPI Schema with Swagger UI

[Abh1ramManugur1]

Addresses #418

Incorporated new drf-spectacular module to render OpenAPI Spec, as a result new nested serializers had to be added to serializers.py

Extended schema to incorporate view functions not automatically caught by drf-spectacular, excluded transient get legacy endpoint

[manning-ncsa]

This looks great so far! I'm experimenting with the interactive feature. By copying the sessionId from the auth cookie, I was able to interactively query and create an Alias object. I also verified that it appears on the transient result page.

[manning-ncsa]

Please use a code linter like flake8 and autopep8 in your IDE so we don't have to make commits like cfb5d4e.

[manning-ncsa]

Are the new serializer functions like CutoutNestedSerializer independent of the originals like CutoutSerializer used by the /api/[object] endpoints? We need to ensure if possible that there is only one serializer defined per model because otherwise we risk a divergence between the OpenAPI spec and the actual API responses.

[Abh1ramManugur1]

They are independent. I introduced the nested serializers to address warnings with the drf-spectacular module that were occurring due to the default name for nested serializers simply being 'NestedSerializer' leading to conflict and incorrect output on swagger-ui. That being said these aren't strictly necessary, as without them swagger ui would not display nested serializers properly which may be acceptable for our usage of it.