Remove IHMP dependency from org 1

### Need:
- To reduce the code complexity to make developer/implementor/QA life simple
- To provide the flexibility to change the forms in child orgs

### Why should it be done by product team again:
- Since we know the code context better we can better predict if would any issues arise and have a better plan.
- Also this is the last org that would need such major changes

### Acceptance criteria:
Similar to [CK]https://github.com/avniproject/avni-product/issues/1523) now remove for IHMP.

The issue names no files, tests, or entry points. Start by reviewing the referenced CK issue, avni-product#1523, and compare its approach with the IHMP organization context in avni-server. Done means removing the IHMP dependency while preserving the stated flexibility for child-organization forms.

Written by the indexing model from the issue text.