Initialize IPP pii_from_user with user UUID

[aduth]

Why: Because it's a required attribute for the real resolution vendor implementation, which otherwise fails without it.

[aduth]

Syncing this to the real vendor implementation should help surface the issue in feature specs.

identity-idp/app/services/proofing/lexis_nexis/instant_verify/proofer.rb

Lines 8 to 18 in fee0abe

	required_attributes :uuid,
	:first_name,
	:last_name,
	:dob,
	:ssn,
	:address1,
	:city,
	:state,
	:zipcode
	optional_attributes :address2, :uuid_prefix, :dob_year_only

[tomas-nava]

this test is failing on this branch (locally and on GitLab); haven't investigated why yet:

bundle exec rspec spec/features/saml/ial2_sso_spec.rb:143

[aduth]

@tomas-nava Taking a look at that one now. The other spec failures for agent_spec.rb are legit, since we weren't fully stubbing an applicant for those. Regardless we may be able to get past it by reverting the changes to the mock client, even if it leaves us without much regression assurances.

[aduth]

The issue with ial2_sso_spec turned out to be a real, identical issue impacting another usage of the resolution vendors which also wasn't passing UUID (fixed in 24ed078). It likely hasn't been noticed 'til now since the specific functionality (re-sending a letter after it "bounces") is not enabled in any environment, even local development.

[svalexander]

just for clarification - address1 is the street address correct?

[aduth]

Yeah we populate it through the Idv::AddressForm (Address step):

identity-idp/app/forms/idv/address_form.rb

Line 6 in 17eddab

ATTRIBUTES = %i[state zipcode city address1 address2].freeze

identity-idp/app/forms/idv/address_form.rb

Lines 34 to 42 in 17eddab

	def consume_params(params)
	params.each do |key, value|
	raise_invalid_address_parameter_error(key) unless ATTRIBUTES.include?(key.to_sym)
	send("#{key}=", value)
	if send(key) != @pii[key] && (send(key).present? || @pii[key].present?)
	@address_edited = true
	end
	end
	end

[zachmargolis]

LGTM