Support $import OperationOutcomes written when a Success

[prb112]

Is your feature request related to a problem? Please describe.
Support $import OperationOutcomes written when a Success

The current behavior only stores the Error/Warning conditions on a Failure to $import.

{
    "transactionTime": "2021-05-19T19:33:28.828Z",
    "request": "https://localhost:9443/fhir-server/api/v4/$import",
    "requiresAccessToken": false,
    "output": [
        {
            "type": "OperationOutcome",
            "url": "fE66-QcWbrCnzF2sEVmI7Z_m4lKG-S_J4h4r8HvzcuQ/Patient_1.ndjson_oo_success.ndjson",
            "count": 1
        }
    ],
    "error": [
        {
            "type": "OperationOutcome",
            "url": "fE66-QcWbrCnzF2sEVmI7Z_m4lKG-S_J4h4r8HvzcuQ/Patient_1.ndjson_oo_errors.ndjson",
            "count": 1
        }
    ]
}

Describe the solution you'd like
For S3/File import, we want to write Success Outcomes.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Acceptance Criteria
1.
GIVEN a Successful Import
AND at least one Warning
WHEN $import is started
AND $import is completed
THEN **oo_success.ndjson is created.
AND there is at least one OperationOutcome for the Successful Import

Additional context
Found in #2083

I suspect this is a 2 pointer.

[prb112]

QA is the same as #2910

[d0roppe]

The import with errors does not fill in the errors file of type ndjson. Following the QA info written up in issue 2910

[d0roppe]

the error file now has information on what the error wss and from what line number from the input file.