Support apiMaturity on all XML constructs #1608
Description
Right now we support apiMaturity on a few things (clusters, attributes, commands), but it would be good to have it on all constructs: all fields, enum values, etc, etc.
Certainly if it has a "Conformance" column in the spec (and hence can be marked provisional), it should be able to have apiMaturity flagged on it.
This will probably need support in the ZAP DB and whatnot.