handle creator parsing with comma

[ogmanojdev]

Fix: Split from the right, not the left

Since the format is:

Name[,Email[,URL]]

Email and URL (if present) are always at the end. So we should split from the right using rsplit(",", maxsplit=2)

[rajna-fani]

I tested the rsplit(",", maxsplit=2) approach locally against a few realistic --creator inputs. It only fixes a narrow case (when all 3 fields are provided and the name has exactly one comma), but leaves other common cases broken and can even make multi-comma names worse.

Examples:

• "Google, LLC"

  • current (split): {"name": "Google", "email": "LLC"} (wrong)
  • this PR (rsplit): {"name": "Google", "email": "LLC"} (still wrong)

• "Google, LLC,info@google.com"

  • current (split): {"name": "Google", "email": "LLC", "url": "info@google.com"} (wrong)
  • this PR (rsplit): {"name": "Google", "email": "LLC", "url": "info@google.com"} (still wrong)

• "Google, LLC,info@google.com,https://google.com"

  • current (split): wrong
  • this PR (rsplit): correct (this is the one case that improves)

• "Doe, Jr., John,john@example.com"

  • this PR (rsplit) produces incorrect field assignment (multi-comma names get worse)

Root issue: comma is an ambiguous delimiter (it can be part of a valid organization/person name). Splitting from the left vs right cannot fully resolve that ambiguity.

Potential solution direction: support an unambiguous delimiter (e.g., semicolons) for the structured form (Name;Email;URL). That would align better with Croissant’s intent that creator is a structured Person/Organization object, but the CLI input format needs a delimiter that can’t also be part of the name.

Also, it would be great to add tests covering comma-in-name cases.

[rafiattrach]

I think the biggest blocker is what @rajna-fani's mentioned above

[ogmanojdev]

added ; as preferred delimiter and added a test case covering all mentioned cases, tested that its passing