Docs: derived data description should be in q&a

[dbirman]

User story

As a user I want to know how derived data_descriptions are generated, that information is currently missing from the documentation

https://aind-data-schema.readthedocs.io/en/latest/data_description.html

Acceptance criteria

• [ ] Q&A for data_description includes docs for derived assets.

Sprint Ready Checklist

• [ ] 1. Acceptance criteria defined
• [ ] 2. Team understands acceptance criteria
• [ ] 3. Team has defined solution / steps to satisfy acceptance criteria
• [ ] 4. Acceptance criteria is verifiable / testable
• [ ] 5. External / 3rd Party dependencies identified
• [ ] 6. Ticket is prioritized and sized

Notes

Add any helpful notes here.

[dbirman]

Note from David: "Generally it's on the processing pipeline to make one. Most reliable way I have seen is to the take the input data description, apply aind-metadata-upgrader to upgrade in case it's an older version, and call DerivedDataDescription.from_data_description. data_description_upgrade.py AllenNeuralDynamics/aind-metadata-upgrader"

[saskiad]

Not all derived assets come via a pipeline. Documentation needs to be clear for other users