Remove unnecessary clone in node update method

[Ubitso]

:memo: Description

We have a lot of instances of the app, with a bunch of services. When app starts it took too long(4 sec on average) of active node cpu workload. I've used the node debug to find a hot spot. That was a deepClone in update method of node.js. It might be not necessary to clone the object because it comes from transport and it isn't used after. I think current tests it has to be enough to prove that everything ok with the registry

:gem: Type of change

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

:vertical_traffic_light: How Has This Been Tested?

It has to be enough current tests of node-catalog

:checkered_flag: Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my own code
• [ ] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [ ] I have commented my code, particularly in hard-to-understand areas

[Ubitso]

[Ubitso]

I've found cloneDeep was used to omit handler properties from services object. It breaks CBOR serializer e2e tests.

[Ubitso]

@icebob Can you look this PR, please?