Update handling of Ember Record Identifiers

[dvonanderson]

Closing issues

closes #481

Pull Request

• Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
    - [ ] Docs have been added / updated (for bug fixes / features)

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

• This is a feature update that introduces using the uuid for contacts, dictionaries, and records to become the Ember internal identifier.
• This is the first step of validating existing records that may exist and now we can either update those records with new information or alarm the user of an existing record
• Updated a few dependencies
• Upgraded to use Yarn v4 for better package resolutions.

• What is the current behavior? (You can also link to an open issue here)
  Prevent and cleanup duplicate records #480
  Assign ember record identifiers ("id") based on UUID's #481

• What is the new behavior (if this is a feature change)?

• On any imported data sets that is not MdJson, we will now use the uuid identifier to create Ember internal identifiers.

[hmaier-fws]

Seems to work as intended