FhirPathEngine should use existing ValidationSupport instead of init again

[maimoonak]

Describe the Issue

The line where we are generating FhirPathEngine creates a new instance of DefaultProfileValidationSupport which occupies more than 17MB. If this is init into app anywhere again it keep multiplying and causes a performance lag. The method getValidation context into FhirContext does it automatically hence this should use validationSupport from FhirContext.

Impact on app.
Around 500MB performance impact was noticed in profiling with doing this.

Before

After

Would you like to work on the issue?

yes

[jingtang10]

@maimoonak do you have a proposed fix for this?

[maimoonak]

Done in #1328

[Tarun-Bhardwaj]

Closing the issue as per discussion with Maimoona.