GET Resolved Profile Returns Content Incorrect

[brian-comply0]

The specification for GET /profile/{identifier}/resolved-catalog method/endpoint should return a valid OSCAL catalog in XML, JSON and YAML formats.

Revised: 2024-03-25

[brian-comply0]

2024-02-07 deferring until controls internal MVP is achieved. Moving to next sprint just to track.

[brian-comply0]

The fix for GET /profile/{id}/resolved-catalog looks great!
@brian-comply0 missed that this should also be fixed for GET /profile/{id}/resolved-snapshot/{id}

[brian-comply0]

This is now addressed for both GET /profile/{id}/resolved-catalog and GET /profile/{id}/resolved-snapshot/{id} in PR #72.
The XML returns for each of these suffers the same problem described in issue #78 and should be addressed as part of that issue. Closing this one.