Conformance classes inconsistency

[m-mohr]

Some conformance classes have a trailing slash (sometimes before a fragment) and sometimes not.
For example sort is https://api.stacspec.org/v1.0.0-beta.4/item-search/#sort although it seems from the spec that it should be https://api.stacspec.org/v1.0.0-beta.4/item-search#sort

[m-mohr]

There seem to be a couple more things inconsistent: #417

[geospatial-jeff]

I think this may have been fixed but I'd like to do one more pass through all of the conformance classes after #432 is finished.

[gadomski]

I checked both backends locally and they look fine. I'm going to close this a fixed pre-2.4.4, please reopen if there's incorrect conformance classes found.

[m-mohr]

@gadomski Looks better now, but I just found that at least MSPC still uses strange CQL Text/JSON conformance classes.
Not sure whether that's a MS PC or a STAC Fastapi bug though as I don't use STAC Fastapi myself.

• MSPC: https://api.stacspec.org/v1.0.0-rc.1/item-search#filter:cql-text and json equivalent
• The Filter extension indicates: http://www.opengis.net/spec/cql2/1.0/conf/cql2-text and json equivalent

Edit: But it seems the wrong (old?) ones are listed here as well: https://stac-utils.github.io/stac-fastapi/api/stac_fastapi/extensions/core/filter/filter/#filterextension

Edit 2: Opened #539

[gadomski]

Yup, I think you're right but will ask Phil to check to make sure (over on the new issue).