chore: Initial seed setup of MICROSTRUCTURE ontology

Auto-generated via 'Setup New Ontology' GitHub Actions workflow:
- Configured project-odk.yaml (URI base: https://w3id.org/pmd/microstructure/)
- imports-edit.owl aggregates all *_import.owl modules
- microstructure-shared.owl imports imports-edit.owl (shared base for all components)
- Each microstructure-{component}.owl imports microstructure-shared.owl with annotations
- microstructure-axioms-shared.owl imports ALL unique component files (no duplicates)
- Generated microstructure-edit.owl (ontology source) and microstructure-idranges.owl
- Initialized ROBOT template TSV files in src/templates/

Author: github-actions[bot]

CONTRIBUTING.md

@@ -0,0 +1,86 @@
+# Contributing to DiStEL Microstructure Ontology
+
+:+1: First of all: Thank you for taking the time to contribute!
+
+The following is a set of guidelines for contributing to MICROSTRUCTURE. 
+These guidelines are not strict rules. Use your best judgment, and feel free to propose 
+changes to this document in a pull request.
+
+## Table Of Contents
+
+- [Guidelines for Contributions and Requests](#contributions)
+    * [Reporting problems with the ontology](#reporting-bugs)
+    * [Requesting new terms](#requesting-terms)
+    * [Adding new terms by yourself](#adding-terms)
+- [Best practices](#best-practices)
+    * [How to write a great issue?](#great-issues)
+    * [How to create a great pull/merge request?](#great-pulls)
+
+<a id="contributions"></a>
+
+## Guidelines for Contributions and Requests
+
+<a id="reporting-bugs"></a>
+
+### Reporting problems with the ontology
+
+Please use our [Issue Tracker](https://github.com/materialdigital/materialdigital/microstructure-ontology/issues/) for reporting problems with the ontology. 
+To learn how to write a good issue [see here](#great-issues).
+
+<a id="requesting-terms"></a>
+
+### Requesting new terms
+
+Before you write a new request, please consider the following: 
+
+- **Does the term already exist?** Before submitting suggestions for new ontology terms, check whether the term exist, 
+either as a primary term or a synonym term. You can search for your term using [OLS](http://www.ebi.ac.uk/ols/ontologies/microstructure).
+- **Can you provide a definition for the term?** It should be very clear what the term means, and you should be
+able to provide a concise definition, ideally with a scientific reference.
+- **Is the ontology in scope for the term?** Sometimes, it is hard to tell whether a term "belongs" in
+and ontology. A rule of thumb is "if a similar term already exists, the new term is probably in scope."
+It can be very helpful to mention a very similar concept as part of the term request!
+
+#### Who can request a term?
+
+Anyone can request new terms. However, there is not guarantee that your term will be added automatically. Since this is a 
+community resource, it is often necessary to do at least some of the work of adding the term yourself, see below.
+
+#### How to write a new term request
+
+Request a new term _via_ the GitHub [Issue Tracker](https://github.com/materialdigital/materialdigital/microstructure-ontology/issues/).
+
+It is important to remember that it takes a lot of time for curators to process issues submitted to the tracker.
+To make this work easier, please always use issue templates if they are available (https://github.com/materialdigital/materialdigital/microstructure-ontology/issues/new/choose).
+
+For how to write a good term request, please read the [best practices carefully](#great-issues).
+
+<a id="adding-terms"></a>
+
+### How to add a new term
+
+If you have never editted this ontology before, first follow a [general tutorial](https://oboacademy.github.io/obook/lesson/contributing-to-obo-ontologies)
+
+**Process**:
+
+1. Clone the repository (In case you are not an offical team member, create a fork first)
+1. Create new branch in git, for example `git checkout -b issue123`
+1. Open src/ontology/microstructure-edit.owl in your favourite editor, i.e. [Protege](https://protege.stanford.edu/). **Careful:** double check you are editing the correct file. There are many ontology files in this repository, but only one _editors file_!
+1. Perform your edit and save your changes
+1. Commit changes to branch
+1. Push changes upstream
+1. Create pull request
+
+## Best Practices
+
+<a id="great-issues"></a>
+
+### How to write great issues?
+
+Please refer to the [OBO Academy term request guide](https://oboacademy.github.io/obook/howto/term-request/).
+
+<a id="great-pulls"></a>
+
+### How to create a great pull/merge request?
+
+Please refer to the [OBO Academy best practices](https://oboacademy.github.io/obook/howto/github-create-pull-request/)

issue_template.md

@@ -0,0 +1,21 @@
+For new term requests, please provide the following information:
+
+## Preferred term label
+
+(e.g., Asplenia)
+
+## Synonyms
+
+(e.g., Absent spleen)
+
+## Textual definition
+
+the definition should be understandable even for non-specialists. Include a PubMed ID to refer to any relevant article that provides additional information about the suggested term.
+
+## Suggested parent term
+
+Please look in the hierarchy in a browser such as [OLS](http://www.ebi.ac.uk/ols/ontologies/microstructure)
+
+## Attribution
+
+If you would like a nanoattribution, please indicate your ORCID id