(DRAFT) Add @property to portfolio related fields in Domain Requests

[CocoByte]

Issue description

With the introduction of org model, certain fields stored in Domain Requests are now stored in Portfolios. In order to avoid duplication of data, Org Model domain requests should not directly store data already present in their associated portfolio. Instead, we will add @property to the relevant fields so that Org Model domain requests reference Portfolio data.

Acceptance criteria

Update the following Domain Request fields to point to equivalent Portfolio fields if the Domain Request is an org model request.

• organization_name
• generic_org_type (called "organization_type" in Portfolio)
• notes
• federal_agency
• federal_type
• senior_official
• address_line1
• address_line2
• city
• state_territory
• zipcode
• urbanization
• security_contact_email

Additional context

No response

Links to other issues

No response

[CocoByte]

@abroddrick I am unsure if "Notes" should also have @-parameter for it. Also, I am ignoring some fields like "about_your_organization" as well as fields related to federal_type (such as "federally_recognized_tribe" and "state_recognized_tribe") since these do not show up in portfolios...do you have any thoughts on how we should approach these non-portfolio fields?

[h-m-f-t]

I think we'll want to have tribal information as part of the org model eventually (i.e., it maybe should have @ parameter) but I defer to engineering on the need for this now.

[h-m-f-t]

Adding refinement simply because it's still marked draft and we've moving it out of new.