Publish new STAC examples

[cholmes]

#955 has a new structure for examples, that consists of two complete navigable catalogs. They 'work' in github, but we'd have to keep updating the 'self' links.

A better approach would be to publish the examples, just like we do with the schemas. Could use examples.stacspec.org to mirror the structure, as we probably would want to use the same versioning. We should also consider putting up a STAC Browser, either at the root of that, or else stacspec.org/examples.

If we do this we should also move the 'assets' to the same location, as they are just a random google cloud bucket at the moment.

Doing all this would let us keep the github version as a 'self-contained' catalog, that would work locally when a user checked out the repo, and then the published one can be an absolute catalog (ideal, but we need to rewrite all the URL's), or relative published catalog (just change the self links at the root). This would be better, so that all versions of the catalog fit our recommendations, and even show how the same catalog is represented in each.

[m-mohr]

Is the version number update really a problem? Whether search & replace works on 100 or 200 matches in the files doesn't really care, right?