Description of problem:

Export paths are inconsistent for Library exports from two different organizations.

How reproducible:

always

Is this issue a regression from an earlier version:

No, it's reproducible in 6.17.4 too.

Steps to Reproduce:

1. On a blank Sat, create two orgs, let say Primary and Secondary.
2. In each org, create a product and a custom repo and sync both.
3. Export the Library from the Primary org.
4. Export the Library from the Secondary org.

Actual behavior:
The first export gets stored in /var/lib/pulp/exports/Primary/Export-Library/1.0/<datetime>
The second and any consequential export gets stored in /var/lib/pulp/exports/Primary/<uuid>/1.0/<datetime>

[root@sat exports]# hammer content-export complete library --organization-id="3"
[....................................................................................................................................................................................................................................] [100%]
Generated /var/lib/pulp/exports/Primary/Export-Library/1.0/2025-09-15T12-11-15-04-00/metadata.json

[root@sat exports]# hammer content-export complete library --organization-id="4"
[....................................................................................................................................................................................................................................] [100%]
Generated /var/lib/pulp/exports/Secondary/d54c4913-8a9d-4e95-a8fe-6fcbb9fb5da7/1.0/2025-09-15T12-11-28-04-00/metadata.json

Expected behavior:

Consistent export paths across organizations: /var/lib/pulp/exports/<org_name>/Export-Library/<version>/<datetime>

Business Impact / Additional info:

Although the customer impact is probably small, it will cause test failure in CI when Library exports are exercised from different tests.