Support schemaUri property of EXT_structural_metadata

[azrogers]

As noted in #727, though EXT_structural_metadata can specify a schemaUri that contains the URI of a JSON file to load instead of the embedded schema, we don't currently support this property. This change adds that support.

As part of the change, I gave the generate-classes tool some idea of what a "shared asset" is, so it can now generate a shared asset property directly rather than needing to mess with derived classes like in the case of Image/ImageSpec. The largest change, by lines of code, is that a getSizeBytes method is now generated for every type. This is necessary for the SharedAssetDepot to know when it's "full."

Code needs cleanup, especially the JavaScript code which I don't have a formatter set up for. Also need to test in each of the runtimes - if there's any changes needed, they'll be small, but I haven't checked yet.

[kring]

@azrogers this looks great! There are just some details in the generated getSizeBytes implementations that need to be worked through.

[azrogers]

@kring Updated the code generation based on your comments, should be good for another look when you get the chance!

[kring]

Looking good, just a little more getSizeBytes nitpicking! Also, don't forget that all of the implementations of that method need to chain to their base class (usually ExtensibleObject) implementation, too!

[azrogers]

@kring Just letting you know this should be good for another look!

[kring]

Nearly there! Just one tricky getSizeBytes situation left that I'm going to take a quick look at myself.

[azrogers]

@kring Updated the doc comments and added const to those for(auto& ... loops!

[kring]

All changes look good! But I tried regenerating the 3D Tiles (npm run generate-3d-tiles) and quantized-mesh (npm run generate-quantized-mesh-terrain) classes, and the generated code has compiler errors in both cases.