Subscribe by id Integer32 implementation

[rafaeling]

A variation of the Subscribe method which improves performance by using an Integer32 ID instead of a string for signals parameter.

[codecov]

Codecov Report

Attention: Patch coverage is 83.50000% with 33 lines in your changes missing coverage. Please review.

Project coverage is 55.33%. Comparing base (7b47ed9) to head (a8df2f6).
Report is 4 commits behind head on feature/databroker-api-v2.

Files with missing lines	Patch %	Lines
databroker/src/grpc/kuksa_val_v2/val.rs	83.33%	33 Missing ⚠️

Additional details and impacted files

@@                      Coverage Diff                      @@
##           feature/databroker-api-v2      #81      +/-   ##
=============================================================
+ Coverage                      54.99%   55.33%   +0.33%     
=============================================================
  Files                             33       33              
  Lines                          14525    14677     +152     
=============================================================
+ Hits                            7988     8121     +133     
- Misses                          6537     6556      +19     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[lukasmittag]

Looks good not tested yet. Just one comment. Will try to test and start today as well.

[argerus]

This is PR is changing way more than necessary. Databroker already supports the concept of using id instead path to refer to signals.

This is for example used by providers in the sdv.databroker.v1 interface.

To add support for this in kuksa.val.v2, you should in theory only need to change stuff under grpc/kuksa_val_v2.

[erikbosch]

LGTM

This should not be merged

[erikbosch]

LGTM

[erikbosch]

@argerus - can you check if you are happy with it now