Stefan Apfel

For the incremental Schema Loading, I could imagine we can query that information on the class stubs and construct the tree internally, even if the items not fully loaded yet....

It seems the only time we need that SchemaContextEditor in the SchemaEditChangeBase implementations is to [add the edit info](https://github.com/iTwin/itwinjs-core/pull/6997/files#diff-ee30444bedc1125a5eff46d8f11706a927c16810a45c587abdd6f9796d021244R77) (and to call [changeCancelled](https://github.com/iTwin/itwinjs-core/pull/6997/files#diff-ee30444bedc1125a5eff46d8f11706a927c16810a45c587abdd6f9796d021244R147). I think it would be cleaner if...

After changes became edits, we need to update a few more places (file names, properties and methods especially in ChangeInfo/Options) :)

This PR contains a couple of changes that seem to be useful (like the contextural conflict interfaces) others might break existing consumers (eg when changing the conflict codes) so, before...

I converted the PR as draft, since we won't work on that in the short future.

Don't forget to do an extract-api, we changed a few interfaces.