The returned HTTP status code from uploading a BOM should be 202

### Current Behavior:

Uploading a BOM returns a status code of 200 OK

### Proposed Behavior:

With the asynchronous nature of processing I think a 202 Accepted response would be more appropriate.

But it could have impacts for any tooling which depends specifically on 200 vs just checking for a 2xx success response code. So feel free to close it without discussion. The value in changing this behavior isn't really there. But it might make a good first issue for someone and helps reinforce the asynchronous nature of BOM processing.

Start by locating the API entry point that handles BOM uploads and inspect its existing response-status tests, if present. Confirm how asynchronous processing is exposed, then verify that successful uploads return 202 and that relevant tooling or tests do not rely specifically on 200.

Written by the indexing model from the issue text.