Profiler error handling

[galtm]

Another attempt at rebasing the previously reviewed PR #1549. The base is develop and all the files I changed are under src/utils/resolver-pipeline. There are 2 commits:

• 18d52fa - recreating the work from 1549, off the current state of the develop branch
• 1b1068f - changing 3 directory paths now that the profile resolver code has changed its directory hierarchy

I ran all the profile resolver XSpec tests in Oxygen and there are no failures.

@aj-stein-nist : Is this pull request a reasonable replacement for #1549, or does #1943 have some advantage?

Committer Notes

{Please provide a brief description of what this PR accomplishes. Be sure to reference any issues addressed. If the PR is a work-in-progress submitted for early review, please include [WIP] at the beginning of the title or mark the PR as DRAFT.}

All Submissions:

• Have you selected the correct base branch per Contributing guidance?
• Have you set "Allow edits and access to secrets by maintainers"?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you squashed any non-relevant commits and commit messages? [instructions]
• Do all automated CI/CD checks pass?

By submitting a pull request, you are agreeing to provide this contribution under the CC0 1.0 Universal public domain dedication.

(For reviewers: The wiki has guidance on code review and overall issue review for completeness.)

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you included examples of how to use your new feature(s)?
• Have you updated all OSCAL website and readme documentation affected by the changes you made? Changes to the OSCAL website can be made in the docs/content directory of your branch.

[aj-stein-nist]

Thanks for this @galtm, I tested locally and it looks good to me.