Support Friendly URLs for documents

[tuckerzp]

Rather than loading by OscalURL's in the editor, we now load based on
the OSCALObjects uuid. This allows for a lot more coherent way of
routing throughout the editor. It also allows you to load an element by
placing the uuid in the url.

This may render some portions of the OSCALLoader redundant. As I still do not
feel completely confident on what everything in the OSCALLoader does, please
pay extra attention in case I missed something.

Testing still needs to be added to this, but the functionality should
be working. It makes more sense to deal with this testing in EasyDynamics/oscal-editor-deployment#98

Closes #336

[kylelaker]

On the whole... wow! Love it! I think there are some small adjustments we can make to reduce duplication further.

[kylelaker]

Okay so it looks like there is an odd behavior here.

Steps to Reproduce

1. Launch the editor, go to any OSCAL Document type (for this example, Catalog)
2. Choose a catalog from the drop down
3. Wait for the catalog to load (or don't)
4. Go to the navigation
5. Click the same OSCAL document type (in this example, Catalog)

Expected Behavior

The page is blank except for the LoaderForm.

Actual Behavior

The previous document remains on the page.

[tuckerzp]

Expected Behavior
The page is blank except for the LoaderForm.

Actual Behavior
The previous document remains on the page.

I agree that it doing that would make sense but I am not 100% sure this is an issue that needs to be solved here. #472 will get rid of the ability to click on a OSCALType like that. So going to just catalog will no longer be possible. Making this behavior impossible to replicate.

With that said, I also think that what we push to develop should be a working version of the editor. But it seems that Develop also has this same behavior. Although this branch does remove the OSCALLoaderForms data.

I am fully open to working on fixing this, I just wanted to be sure that it is something worth fixing on this pr.

[Bronstrom]

Expected Behavior
The page is blank except for the LoaderForm.

Actual Behavior
The previous document remains on the page.

I agree the actual behavior is odd, but with it being carried over from develop it seems more logical to fix in a separate PR. Although, I lean towards skipping over addressing this issue with #472 already in development and changing the user interaction of selecting OSCAL documents.

[kylelaker]

@tuckerzp Please ensure that all supporting PRs on other repos are merged before we merge this in. Tests in oscal-editor-deployment aren't strictly necessary but I don't want regressions in the REST service or Docker container because of this PR

[Bronstrom]

This is looking great to me and I like the choices made to limit redundancy with the app bar and navigation routes! It appears all supporting PRs (titled as "Support Friendly URLs" across other repos) have been merged, so I will go ahead and merge this PR.