Make ui:order less strict

[mfulton26]

Throwing an error when an extraneous property name is included
or when a property name is missing is problematic when ordering
properties in a dynamic schema (e.g. via schema dependencies,
etc.).

This change ignores extraneous property names and places places
missing properties at the end if not specified.

Reasons for making this change

[Please describe them here]

If this is related to existing tickets, include links to them as well.

Checklist

• I'm updating documentation
  • I've checked the rendering of the Markdown text I've added
  • If I'm adding a new section, I've updated the Table of Content
• I'm adding or updating code
  • I've added and/or updated tests
  • I've updated docs if needed
  • I've run npm run cs-format on my branch to conform my code to prettier coding style
• I'm adding a new feature
  • I've updated the playground with an example use of the feature

[glasserc]

Refs #823, #814. Per the discussion in the other threads, I think doing this unconditionally is dangerous. I'd much rather be smart about it.

[mfulton26]

I just got done looking at those refs. Thank you. If I understand correctly, you would like for an error to be shown for any extraneous property name that is not in the schema properties nor any conditional schema properties defined in dependencies. That seems doable.

[epicfaace]

I just got done looking at those refs. Thank you. If I understand correctly, you would like for an error to be shown for any extraneous property name that is not in the schema properties nor any conditional schema properties defined in dependencies. That seems doable.

@mfulton26 I'm closing this for now, if you would like to implement the behavior mentioned above, please make another PR. Thanks