Fix .US domain parser & add .JP registrar support

[usiegj00]

Fix .US Domain Parser & Add .JP Registrar Support

This PR includes two important parser fixes:

1. Fix .US Domain Parser for ICANN-Compliant Format

Problem

The .us domain parser was failing because it was using BaseShared2 which was designed for the old NeuStar format (pre-2015). The .US registry has since transitioned to Registry Services, LLC and now uses ICANN-compliant WHOIS format.

Solution

• Changed parser from BaseShared2 to BaseIcannCompliant
• Added custom status handler to return actual EPP codes as an array

2. Add Registrar Property Support for Japanese (.jp) Domains

Problem

The Japanese (.jp) WHOIS parser was missing registrar information extraction.

Solution

• Added registrar property parsing for whois.jprs.jp responses
• Includes test fixtures and specs

Background

The .us registry changed their WHOIS format sometime after 2014:

Old format (NeuStar, pre-2015):

Domain Name:                                 GOOGLE.US
Sponsoring Registrar:                        MARKMONITOR, INC.
Domain Registration Date:                    Fri Apr 19 23:15:57 GMT 2002

New format (Registry Services LLC, current):

Domain Name: google.us
Registrar: MarkMonitor, Inc.
Creation Date: 2002-04-19T23:16:01Z
Registry Expiry Date: 2026-04-18T23:59:59Z

Changes

1. Parser now uses BaseIcannCompliant base class
2. Custom status property returns EPP codes as array: ["clientDeleteProhibited", "serverTransferProhibited"]
3. Updated test fixtures with current NASA.us data

Verification

Tested with multiple .us domains, all return ICANN-compliant format:

• google.us ✅
• nasa.us ✅
• whitehouse.us ✅

# Test the parser:
bundle exec rspec spec/whois/parsers/responses/whois.nic.us/us/

References

• ICANN's WHOIS Data Directory Services Updates
• Registry operator changed from NeuStar to Registry Services, LLC (about.us)