[External API][Performance] Make retrieving catchment optional

[vinayvenu]

GET /api/subject/#id takes up about 16% of the resources on the common cloud, and is slow (median response time 3.3 seconds). More than 90% of the time and resources are taken up because we are trying to retrieve all catchments the subject belongs to. Making this configurable can make the API at least 10 times more efficient. Overall improvement in Avni performance will be is around 14%.

Acceptance criteria

• Add a parameter "includeCatchments" (values true, false) to the GET api/subject/#id api.
• By default, do not fetch the "catchments" field if this is not set to true

[petmongrels]

Introducing a breaking/forcing change by making the includeCatchments = false. So that only people who require catchment pass it explicitly. Making it true will mean we not get performance benefit unless people make change.

[vinayvenu]

Context, as far as we know catchments are used only for the Bahmni HWC integration. Not sure if it is still being used after the pilot.