REST API Error Handling Improvements & Import of dtnma-tools SQL concurrency fix

[DavidEdell]

Updated REST APIs to return correct error codes, and updated dtnma-tools to bring in fixes for SQL concurrency causing reliability issues.

NOTE: Testing is still in progress (a final rebuild test after dtnma-tools changes were merged into main was misbehaving on initial quick look).

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[BrianSipos]

The compose logs don't say it clearly but the container which is logged as being "... Created" but does not show up as "... Healthy" is the anms-ui one.

[DavidEdell]

The compose logs don't say it clearly but the container which is logged as being "... Created" but does not show up as "... Healthy" is the anms-ui one.

I noticed that - doubly odd as there haven't been any recent changes within the anms-ui.

I tried another fresh podman build yesterday on my rh VM, this time specifying BUILDAH_FORMAT=docker podman compose --profile full build to force healthcheck availability, and still couldn't reproduce the CI error (podman compose ps showed all containers as healthy).

I also timed the startup, and it came up well within CI's 10 minute timeout window for that step.

There was also an earlier error in podman-CI related to timeouts pulling certain dependencies that resolved on a 'retry failed'. It's increasingly looking like there's something odd with the CI runner VM...

[BrianSipos]

Changes themselves look okay. The anms-core routes that just relay to refdm API should be deprecated for release though.

[BrianSipos]

I tried another fresh podman build yesterday on my rh VM, this time specifying BUILDAH_FORMAT=docker podman compose --profile full build to force healthcheck availability, and still couldn't reproduce the CI error (podman compose ps showed all containers as healthy).
I also timed the startup, and it came up well within CI's 10 minute timeout window for that step.

If there is a more consistent env or command option for podman then the scripts and the CI jobs should use that in the same way.