Bundle documents with string-like reference properties are not handled well

[alexdunnjpl]

Checked for duplicates

No - I haven't checked

🐛 Describe the bug

As can be seen below, some bundles' collection references appear to be string-like rather than array[str]-like. This results in iteration over the characters in a single LIDVID/LID, rather than over the single-element array of LIDVIDs/LIDs.

Need guidance on intended behaviour:

• support string-like reference properties (check and handle gracefully)
• detect, warn-log (to avoid the extra OpenSearch traffic caused by attempting to resolve LIDVIDs for each character)

🕵️ Expected behavior

I expected [...]

📜 To Reproduce

Run ancestry-sweepers against the production CCS remotes (it's currently unclear which one(s))

🖥 Environment Info

• Version of this software [e.g. vX.Y.Z]
• Operating System: [e.g. MacOSX with Docker Desktop vX.Y] ...

📚 Version of Software Used

No response

🩺 Test Data / Additional context

No response

🦄 Related requirements

🦄 #xyz

⚙️ Engineering Details

No response

[alexdunnjpl]

Implement legacy support, as registry-api already includes legacy support and re-ingestion of these products isn't feasible.