Change to RDFC-1.0

[davidlehn]

• Updates to latest "URDNA2015" to "RDFC-1.0" change.
• What is the best way to handle "URDNA2015" algorithm name usage?
  • (a) Do the "warning" thing here? Is that even needed?
  • (b) Add an option, global, or env var to control calling console.trace or a user func if URDNA2015 is used?
  • (c) Alias the "URDNA2015" algorithm name to "RDFC-1.0". The changelog/readme would note the alias, mention the escaping issue between algorithms, note they are otherwise the same. Then do nothing.
  • (d) Fail with unknown algorithm.
• The concern is giving some way to debug where to update where URDNA2015 is used for cases where that may be difficult.
• (c) and (d) are easiest and most straightforward but I'm not sure what the issues will be in practice either way.

[davidlehn]

Decided to try the path of allowing URDNA2015 alias to be explicitly rejected if needed, and to have a developer global to enable tracing where URDNA2015 is used during migration to RDFC-1.0.

[davidlehn]

Merging to main staging branch along with escaping fix branch.