chore: use same metric to expose binary build info

[whynowy]

# HELP build_info A metric with a constant value '1', labeled by Numaflow binary version, platform, and other information
# TYPE build_info gauge
build_info{component="daemon",component_name="simple-pipeline",platform="linux/arm64",version="latest+7450e16.dirty"} 1

# HELP pipeline_build_info A metric with a constant value '1', labeled by Numaflow binary version and platform, as well as the pipeline name. Deprecated: Use build_info instead
# TYPE pipeline_build_info gauge
pipeline_build_info{pipeline="simple-pipeline",platform="linux/arm64",version="latest+7450e16.dirty"} 1

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 6 lines in your changes missing coverage. Please review.

Project coverage is 65.74%. Comparing base (7450e16) to head (6560e81).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
pkg/daemon/server/daemon_server.go	0.00%	3 Missing ⚠️
pkg/mvtxdaemon/server/daemon_server.go	0.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2293      +/-   ##
==========================================
+ Coverage   65.50%   65.74%   +0.23%     
==========================================
  Files         346      346              
  Lines       42493    42497       +4     
==========================================
+ Hits        27837    27939     +102     
+ Misses      13580    13487      -93     
+ Partials     1076     1071       -5     

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