Worker key refresh policy implementation

[manju956]

This feature initiates refresh of worker encryption key pair based on number of work orders processed in case of Singleton worker or number of pre-processed work orders in case of KME worker. A new pair of encryption key is generated in the enclave and the updated enclave signup details are stored in the KvStorage in workers table.

Worker encryption key signature is re-computed when encryption key gets refreshed.

When a worker key gets refreshed during the work order submission, a specific error code is returned to client to indicate worker key refresh. On receiving this error code, client retrieves the updated worker details and does work order submission again.

Signed-off-by: manju956 [email protected]

[lgtm-com[bot]]

This pull request introduces 5 alerts when merging 1df89b3546815fbb2718e64e9a3d1da571aaa5c5 into ed424e717cdd3797f79907ce6ce2e95d0bfe13d4 - view on LGTM.com

new alerts:

• 4 for Unused import
• 1 for Syntax error

[lgtm-com[bot]]

This pull request introduces 1 alert when merging 48318d2a0edc705ba22aef57d4892d9677c467fd into ed424e717cdd3797f79907ce6ce2e95d0bfe13d4 - view on LGTM.com

new alerts:

• 1 for Unused import