Update metadata-service to read water restrictions from Dataverse

# User story
We are deprecating SLIMS as a data provider. Historic water log and restriction data from SLIMS has been migrated to Dataverse. We need to update the metadata-service to read water restrictions from Dataverse instead of SLIMS

# Acceptance criteria
- [ ] Given an endpoint in aind-dataverse-service that fetches water restriction data (https://github.com/AllenNeuralDynamics/aind-dataverse-service/issues/12), add a new raw endpoint for api/v2/dataverse/water_restriction
- [ ] Given a response from aind-dataverse-service that fetches water restriction data, update procedures endpoint to map to aind-data-schema WaterRestriction model (should replace slims call for water restrictions in procedures)
- [ ] (Optional) Deprecate the SLIMS water restriction endpoint and remove it (this can be done in a last ticket as well)

# 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
Use http://aind-metadata-service/api/v2/slims/water_restriction/{example} as an example of the grouping of water restriction data from SLIMS. This data is split up across multiple tables in Dataverse as well