Fix redundancies from extensions: Some classes and properties exist in both extensions and schema.org core

[mfhepp]

Disclaimer: I am not fully up-to-date as for the status of the schema.org extension mechanism. But since vocabulary elements from these extension modules continue to show up on the main schema.org site (which is good, don't change that!), the following conflicts should be resolved:

1. Checking https://raw.githubusercontent.com/schemaorg/schemaorg/main/data/ext/auto/auto.ttl:

• The property https://schema.org/vehicleSpecialUsage is defined in the extension auto/auto.ttl AND in schema.org core.

2. Checking https://raw.githubusercontent.com/schemaorg/schemaorg/main/data/ext/bib/bsdo-1.0.ttl:

• The property https://schema.org/duration is defined in the extension bib/bsdo-1.0.ttl AND in schema.org core.
• The property https://schema.org/pageEnd is defined in the extension bib/bsdo-1.0.ttl AND in schema.org core.
• The property https://schema.org/pageStart is defined in the extension bib/bsdo-1.0.ttl AND in schema.org core.
• The property https://schema.org/pagination is defined in the extension bib/bsdo-1.0.ttl AND in schema.org core.

3. Checking https://raw.githubusercontent.com/schemaorg/schemaorg/main/data/ext/health-lifesci/med-health-core.ttl:

• The class https://schema.org/Dentist is defined in the extension health-lifesci/med-health-core.ttl AND in schema.org core.
• The class https://schema.org/Pharmacy is defined in the extension health-lifesci/med-health-core.ttl AND in schema.org core.
• The property https://schema.org/sponsor is defined in the extension health-lifesci/med-health-core.ttl AND in schema.org core.

4. Checking https://raw.githubusercontent.com/schemaorg/schemaorg/main/data/ext/health-lifesci/physical-activity-and-exercise.ttl:

• The property https://schema.org/category is defined in the extension health-lifesci/physical-activity-and-exercise.ttl AND in schema.org core.

/CC @danbri

Solution: Most likely, the best approach is to simply remove these redundant definitions from the respective extension files (checking that no additional domainIncludes / rangeIncludes will be lost and that the textual definitions are identical).