The project could not be found, but parent project is created and worked fine one month ago

### Current Behavior

Not sure is this output relevant, but I am trying to troubleshoot why is not publishing newest SBOM data from some backed services, all microservices are using our sbom template in Azure CICD pipeline, which mean, template is working correct, but we get error **The project could not be found.** I have checked all missing services stopped to save data at the end of August, not sure did backend developers change something in pipelines, but when I checked template was fine, and same.

In output from below, after my curl, I don't get any other respond, just shell stay like that.

We are using DT v4.8.2, in Azure Service App, with Microsoft SQL server. Also would like to know, DT which resources needs to have, as I see our SQL server is almost hole time DTU 100% utilized, because of CPU 100%. Not sure is some issue in SQL database, or we just created small SQL server.

```
curl --verbose -X POST "https://dt-track-api.azurewebsites.net/api/v1/bom" -H 'Content-Type: multipart/form-data' -H "X-Api-Key: xxxxxxxxxxxxxxxxxxxxxxx" -F "projectName=test-service" -F "parentName=test-service" -F "classifier=Application" -F "projectVersion=rc-1.11111" -F 'bom=@bom.json'

Note: Unnecessary use of -X or --request, POST is already inferred.
* Trying 20.105.224.24:443...
* Connected to dt-track-api.azurewebsites.net (20.105.224.24) port 443 (#0)
* ALPN: offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
* CAfile: /etc/ssl/cert.pem
* CApath: none
* (304) (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted h2
* Server certificate:
* subject: C=US; ST=WA; L=Redmond; O=Microsoft Corporation; CN=*.azurewebsites.net
* start date: Mar 10 03:05:55 2023 GMT
* expire date: Mar 4 03:05:55 2024 GMT
* subjectAltName: host "dt-track-api.azurewebsites.net" matched cert's "*.azurewebsites.net"
* issuer: C=US; O=Microsoft Corporation; CN=Microsoft Azure TLS Issuing CA 02
* SSL certificate verify ok.
* using HTTP/2
* h2 [:method: POST]
* h2 [:scheme: https]
* h2 [:authority: dt-track-api.azurewebsites.net]
* h2 [:path: /api/v1/bom]
* h2 [user-agent: curl/8.1.2]
* h2 [accept: */*]
* h2 [x-api-key: xxxxxxxxxxxxxxxxxxxxxxx]
* h2 [content-length: 474036]
* h2 [content-type: multipart/form-data; boundary=------------------------e0bf8dce9f3d87d3]
* Using Stream ID: 1 (easy handle 0x7fcfa680ae00)
> POST /api/v1/bom HTTP/2
> Host: dt-track-api.azurewebsites.net
> User-Agent: curl/8.1.2
> Accept: */*
> X-Api-Key: xxxxxxxxxxxxxxxxxxxxxxx
> Content-Length: 474036
> Content-Type: multipart/form-data; boundary=------------------------e0bf8dce9f3d87d3
>
* We are completely uploaded and fine
< HTTP/2 408
< content-type: text/html
< date: Tue, 10 Oct 2023 20:41:20 GMT
< content-length: 20
<

```

### Steps to Reproduce

1 tried to upload sbom file via cicd pipeline using curl.

### Expected Behavior

After every commit to get a new sbom file in DT.

### Dependency-Track Version

4.8.2

### Dependency-Track Distribution

Container Image

### Database Server

Microsoft SQL Server

### Database Server Version

_No response_

### Browser

Google Chrome

### Checklist

- [X] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [X] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this defect was already reported