Cleaning up ID range file

[pbuttigieg]

Addressing #1370

Note the more descriptive entries for pattern ranges.

There are pattern definitions (here) that are not allocated clear ranges.

Please create these ranges if you are responsible for the pattern (I see some from @cmungall @turbomam)

• [ ] formation_of_environmental_feature.yaml
• [ ] formation_of_material_entity.yaml
• [ ] formation_of_material_entity_from_input.yaml
• [ ] material_entity_formed_as_result_of.yaml
• [ ] mine.yaml
• [ ] ore.yaml
• [ ] power_plant.yaml
• [ ] soil_by_property.yaml

⚠️ Note the mismatch between the patterns available in YAML and those actually deployed in the module directory. If they're not deployed / used, I'll delete those patterns (or keep them in a archive directory)

@kaiiam you have a range for your pattern generated terms, but this doesn't identify which patterns are used. Could you replace the former with individual ranges for the patterns themselves?

[turbomam]

This looks good to me. Since this PR was created, @aclum and I split up most of

Datatype: idrange:25

    Annotations:
        allocatedto: "National Microbiome Data Collaborative"

    EquivalentTo:
        xsd:integer[>= 3600000 , <= 3600099]

into

Datatype: idrange:28

    Annotations:
        allocatedto: "Alicia Clum"

    EquivalentTo:
        xsd:integer[>= 3600100 , <= 3604999]

Datatype: idrange:29

    Annotations:
        allocatedto: "Mark Andrew Miller"

    EquivalentTo:
        xsd:integer[>= 3605000 , <= 3609999]

[turbomam]

There's currently a merge conflict on

Datatype: idrange:25

    Annotations:
        allocatedto: "Terms generated by design pattern: entity_attributeA"