Implemented REST success, existing param handling

[rgauss]

Creates a handleRestSuccess function and sends that to OSCAL root object renderers as the onRestSuccess property. In the case of OSCALSsp that is passed down to OSCALControlProse and subsequently OSCALRestUtils which executes it on success.

For now the handleRestSuccess simply reloads the entire page. In the future we'll likely want to investigate better re-rendering of specific components.

This also resolves an issue where the set-parameters were being added to the implementedRequirements object rather than replacing an existing one.

[kylelaker]

Eventually for UX reasons, we probably want to consider ways to handle this that aren't as jarring as reloading the whole page (just the component(s) that changed) but this looks good for now!

[rgauss]

Eventually for UX reasons, we probably want to consider ways to handle this that aren't as jarring as reloading the whole page (just the component(s) that changed) but this looks good for now!

Yes, I edited the description this morning with something similar after you had already approved the PR.