Deselected stream properties are not always excluded from `SCHEMA` messages
The extractor select
rules (https://meltano.com/docs/plugins.html#select-extra) are currently only applied to the generated catalog file, and it's up to taps to only include selected properties in their RECORD
messages, which all taps do that support this feature, and their SCHEMA
messages, which not all taps do: many just read the schema from the bundled copy even if not all properties were selected.
This means that when trying to fix an issue with a tap that emits a schema that is not supported by the used target (for example one with column names starting with numbers: tap-facebook#6 (closed)), we cannot currently fix using the select
extra.