[DEA] Reduce the loading time of the subject profile page

[mahalakshme]

Need:

When clicked on a subject enrolled in a program, it takes an around 3-10 secs to finish loading the page which affects the user experience.

AC:

• Reduce the loading of subject profile page(that appears on clicking a subject from search results) independent of the below to less than 2 secs
  • enrolled in program or not
  • with or without completed visits
  • with or without programEligibilityCheckRule or encounterEligibilityCheckRule
  • with or without msgsSent or msgsScheduled
• Many calls(/msgs, /msgsNotYetSent, /programSummaryRule, etc) are made when clicking on a subject(enrolled in a program). Instead do them only when needed or do all without making the screen blocking so that it provides a better user experience when expand icon for something like say programSummaryRule is clicked. Developer can decide.
• Some calls made multiple times. Eg: /programSummaryRule for the same program enrolment loading more than once, calls to /organisationConfig - 3 times. This can also be fixed.

Old: Ignore

Technical Examples:

• /msgs and /msgsNotYetSent need to load only on clicking on expand icon on the profile tab
• /web/subjectProfile?uuid={UUID} looks like also is needed only when clicking on the profile tab or can be split since we fetch things like profilePicture here
• programSummaryRule for the same program enrolment loading more than once - The call can go only when the user opens the ProgramSummary expand icon
• Do /web/forms/formUuid once only when expand icon on Enrolment details is clicked
• /eligibleProgramEncounters and /eligibleGeneralEncounters calls can be made when clicking on 'New Form'. New form can be displayed even if only one encounter present.
• /web/subject/{uuid}/encounters/ called on clicking an individual enrolled in a program, doesn't seem to be used anywhere within or outside of the programs tab.
• calls to /organisationConfig 3 times(on clicking an individual enrolled in a program) can be avoided if managed state better
• So any other API calls made unnecessarily similar to the above:
  1. So make calls only when expand icon is clicked
  2. only for whatever is needed to render the tab/contents user is going to view

Inputs:

split
subject Profule - too much time
take it from user level
calls can be still made