LG-13216: Gaze into the AAMVA SOAP abyss.

[matthinz]

🎫 Ticket

Link to the relevant ticket:
LG-13216

🛠 Summary of changes

#10653 added two new fields to our requests to AAMVA's DLDV service: issue date and expiration date. In manual testing in our staging environment, I discovered that these fields weren't being processed by AAMVA because I used the incorrect namespace in the SOAP XML we were sending. I found it was difficult to keep track of what namespaces our code was referring to because we were labeling them differently from the AAMVA DLDV documentation.

This PR:

1. Updates the namespace abbreviations used in DLDV verification requests to match those used in the AAMVA documentation
2. Fixes the issue date + expiration date fields to use the correct namespaces

Here is what I just said, but in table form:

What we used to call it	What we call it now	What it means
ns2:	nc:	Elements from NIEM core
ns1:	aa:	AAMVA-specific extensions to NIEM core
ns:	dldv:	Elements specifically related to the SOAP interface to DLDV

(I only touched the verification service here--the authentication service is left as-is.)

📜 Testing Plan

I'll be executing this test after merging in the staging environment before this code goes into production:

• Make an AAMVA request including all PII elements from a known good source (first name, last name, license no., issue date, expiry date, dob, and address)
• Verify that all fields are listed in the requested_attributes field on the result
• Verify that all elements are validated by AAMVA
• Repeat this test, altering one PII element at a time and verifying that each item fails appropriately