Create inventory form

[perryr16]

Any background context you want to provide?

Currently, the only way to introduce a new property or tax lot is through a data upload.

What's this PR do?

Introduces a new page available from the inventory nav to create a property or taxlot via a form. When the form is submitted, the backend creates a stub state, view, and property before using the existing "update" endpoint to apply the configured state data passed from the frontend. By using the existing "update" endpoint, we can reuse the same matching/merging/linking functions.

notes:

• If a new property includes tax lot data (jurisdiction tax lot id), a taxlot with that j-id and any other taxlot fields will be created, then linked through a new TaxLotProperty.
• Because a property create is treated as an "update" and not a data upload, the new property will not have a historical entry (building file) on the property detail.
• If a property with a taxlot is created, there will be 2 backend requests, one for a property create and one for a taxlot create.
• If a created property matches a property within the cycle, it is treated as an update and not a merge.

How should this be manually tested?

• Create a new property/taxlot
• Create a property/taxlot that matches an existing record in cycle
• Create a property/taxlot that matches an existing record out of cycle
• Create a property with an associated taxlot via jurisdiction tax lot id. The link should appear on the property detail under "Paired Tax Lots"
• Test validation: duplicate rows, missing matching criteria

What are the relevant tickets?

#4846

Screenshots (if appropriate)