Support for HCA duos_id

[dsotirho-ucsc]

Factored out of #6131 due to the fact that current metadata does not contain this field as of today.

Index project.duos_id, expose in all /index/… responses.

[achave11-ucsc]

Assignee to periodically check for availability of duos_id in snapshots for pilot catalog, or dcpXY catalogs once manage access snapshots are available in prod.

[bvizzier-ucsc]

@dsotirho-ucsc When was the last time this was checked?

Let me know if it isn't there and I'll escalate it.

[dsotirho-ucsc]

@bvizzier-ucsc This was last checked for in dcp42, but I somehow missed the managed access snapshot. Just re-checked and confirmed the duos_id field in project 35d5b057's snapshot.

[achave11-ucsc]

@hannes-ucsc: "Spike to confirm with CC that it is sufficient to return this property in the hits part of the response (no filtering, no sorting, no faceting)"

[dsotirho-ucsc]

Received confirmation from CC that adding the duos_id field to the hits part of the response would be sufficient.

[nadove-ucsc]

@hannes-ucsc: "At least for MA snapshots, the HCA metadata project entity has a DUOS Id property that we will use. For non-MA projects the DUOS Id may be absent, but getting it from TDR as we do for AnVIL would be much more complicated, as it would require a special bundle type, for which we have no support in HCA."

[bvizzier-ucsc]

The requirement for the DUOS ID is to request access for a project via DUOS. As a result, non-MA projects should not require it.

[bvizzier-ucsc]

@hannes-ucsc: "In this case it will be relatively easy to implement."

[dsotirho-ucsc]

Moved to Triage due to the merge of the blocking ticket #6620

[hannes-ucsc]

For demo, show new field in response. Show facets, filtering and sorting by new field.