[admin-api] remains silent when trying to assign an existing accession ID

[aaperis]

Describe the bug

This bug is in the api and should be fixed there
The examples below just makes this easier to test.

We have the restriction that an accession ID should be unique regardless if the user name is different.

If one tries to assign an existing accession ID to a file

Steps to reproduce

./sda-admin file set-accession -filepath requester_demo.org/t1.txt.c4gh -user [email protected] -accession-id my-access-1

then after ingesting a file with a different user:

./sda-admin file set-accession -filepath test_dummy.org/t1.txt.c4gh -user [email protected] -accession-id my-access-1

finalize returns:

{"level":"debug","msg":"Seems accession ID already exists (corr-id: fb84528e-1146-4089-ad64-a09cd494f725, accessionid: my-access-1","time":"2024-12-19T09:34:07Z"}

but sda-admin remains silent.

Expected behavior

• sda-admin returns an informative message to the user
• Tests verifying the fix are added

Additional context

Estimation of size

smal

Estimation of priority

low/medium

[jbygdell]

Moved to admin api since that's where it needs to be implemented.