Improved parsing of WHOIS responses for expiration timestamps

[adrukh]

I noticed the WHOIS parser doesn't extract expiration dates for .it domains.

Example: ailbiella.it

• Raw WHOIS contains Expire Date: 2026-01-20
• rdapper returns expirationDate: undefined

Suggested fix: Add "expire date" (case-insensitive) to the list of recognized expiration field patterns.

Happy to contribute a PR if helpful!

[adrukh]

Another example is google.cn, where the WHOIS record includes Registration Time and Expiration Time - these could also be added to the list of recognized field patterns.

[adrukh]

A weirder example is samete.in.ua, where the WHOIS record includes just expires for the expiration timestamp, which currently isn't picked up by rdapper's parsing.

[jakejarvis]

@adrukh Thank you so much for debugging this and #11! Trying to normalize all of these wildly different responses has made it clear to me why RDAP was needed so badly 😂

[adrukh]

Thank you for an amazingly apt tool for a gnarly problem, and for your responsiveness.
I have an app that does some domain name resolutions, so will keep helping improve the coverage of this bumpy terrain!