cbrelease-4.8.15_RC3: 4.8.14 dev v9 (#594) (#595)

* 4.8.14 dev v9 (#589)

* 4.8.15 dev v1 (#584)

* KB-4705 | DEV| Assessment | BE | Consumption Logic for the QuestionWeightage Assessment Type (#564)

* Added string handling in admin patch API

* Assessment V5 Changes

Assessment V5 Changes

* KB-4705 | DEV| Assessment | BE | Consumption Logic for the QuestionWeightage Assessment Type

1. Removed the hardcoded attributes and added from assessment hierarchy.

* KB-4705 | DEV| Assessment | BE | Consumption Logic for the QuestionWeightage Assessment Type

1. Added proper comments and logs.
2. Refractored the code.
3. Added logic for optionweightage.

---------



* Retry Attempts Enabled for Assessment V5

* KB-4705 | DEV| Assessment | BE | Consumption Logic for the QuestionWeightage Assessment Type (#565)

1. Optional weightage score calculation enhancements.

* Adding the insight API implementation for MDO channel (#571)

* SaveStateMethod

* Maintaining the order of the fields.

* KB-4705 | DEV| Assessment | BE | Consumption Logic for the QuestionWeightage Assessment Type (#580)

1. Enhanchements for questionScheme.

* KB-5130 | DEV| Assessment | BE | Enhancement in Consumption Logic for the QuestionWeightage Assessment Type. (#581)

1. Added logic for new attributes added.
2. Added questionLevel param in Question read API.

* KB-5130 | DEV| Assessment | BE | Enhancement in Consumption Logic for the QuestionWeightage Assessment Type. (#583)

1. Score calculation fix.

---------





* KB-4754:Validation for language, designation fix

* removed changes from cbrelaease-4.8.15

* Modified error message on date of birth validation failure

* changed approach for fetchind and storing data from redis

---------






* KB-4754 changed regex for employee Id to allow all alphabets, updated error message for employee Id containing spaces.

---------

Co-authored-by: ravisaurav-tarento <[email protected]>
Co-authored-by: Sahil-tarento <[email protected]>
Co-authored-by: tarentomaheshvakkund <[email protected]>
Co-authored-by: saipradeep_ravipati <[email protected]>