Develop/feature/td 5925 models caching package changes refactor

[Phil-NHS]

DO NOT MERGE UNTIL STAGE 1 of LHKentia is in Production

Should fail until packages created in production does work locally with 5925 Caching and models package changes

JIRA link

TD-5925

Description

Following changes to the Models and Caching packages LH will need a few changes which are covered in this PR

Screenshots

---

Developer checks

(Leave tasks unticked if they haven't been appropriate for your ticket.)

I have:

• Run the IDE auto formatter on all files I’ve worked on and made sure there are no IDE errors relating to them
  I've tried this with this before and everything breaks
• Written or updated tests for the changes (accessibility ui tests for views, tests for controller, data services, services, view models created or modified) and made sure all tests are passing
• Manually tested my work with and without JavaScript (adding notes where functionality requires JavaScript)
• Tested any Views or partials created or changed with Wave Chrome plugin. Addressed any valid accessibility issues and documented any invalid errors
• [x ] Updated my Jira ticket with testing notes, including information about other parts of the system that were touched as part of the MR and need to be tested to ensure nothing is broken
• [ x] Scanned over my pull request in GitHub and addressed any warnings from the GitHub Build and Test checks in the GitHub PR ‘Files Changed’ tab
  Either:
• [ x] Documented my work in Confluence, updating any business rules applied or modified. Updated GitHub readme/documentation for the repository if appropriate. List of documentation links added/changed:
  • doc_1_here - Willdo after PR
    Or:
• Confirmed that none of the work that I have undertaken requires any updates to documentation

[Phil-NHS]

Dropped elfh here presumed wasnt being used i have done clean rebuild and restore

[Phil-NHS]

@AnjuJose011 @ArunimaGeorge This is stage 2 mostly. The intention is to run CICD vs feature branches make the packages and then this should build in Continuous Integration Check.

I am keeping it separate for now as I want stage 1 out separately unless necessary so to minize impact of roll back fingers crossed wont happen