Update forwarding was not working when entity type is not included in the request

[fgalan]

Considering the following update forwarding request case:

WARN@2023-12-21T09:53:59.504Z AlarmManager.cpp[612]: Releasing alarm BadInput 127.0.0.1
ERROR@2023-12-21T09:53:59.510Z postUpdateContext.cpp[644]: Runtime Error (attribute 'profile_config' not found)
INFO@2023-12-21T09:53:59.510Z logTracing.cpp[231]: Starting forwarding for PUT /v2/entities/device:wt:13@yy/attrs/profile_config
INFO@2023-12-21T09:53:59.511Z logTracing.cpp[296]: Request forwarded (regId: xx): POST http://localhost:1027/v2/op/update, request payload (155 bytes): {"entities":[{"id":"device:wt:13@yy","type":"Device","profile_config":{"type":"command","value":"foobar","metadata":{}}}],"actionType":"update"}, response payload (0 bytes): , response code: 204
INFO@2023-12-21T09:53:59.511Z logTracing.cpp[206]: Request received: PUT /v2/entities/device:wt:13@yy/attrs/profile_config, request payload (170 bytes): {"type":"command","value":"foobar"}, response code: 204

The Runtime Error should not be logged.

[fgalan]

After investigation (see PR #4463) this goes beyond a overlogging error. Issue title changed accordingly.