chore: add critical error metric for numaplane analysis template

[adarsh0728]

What this PR does / why we need it

This is for both Pipeline and MonoVertex. The idea is that we want to improve upon our existing AnalysisTemplates for Numaplane assessment.

The problem with our current assessments is they simply look for any message to get acked. Let's say the first message gets acked, but the second message fails to get acked. Numaplane will call this a success.

If we can have a metric which is able to detect failures like EOT, udf crashes etc, then if any of our new Pipeline Vertices or our new Monovertex has a count > 1, we could fail.

Specifically, the idea is to emit a metric from the numa container whenever there is a critical errors in the numaflow pipeline/monovertex.

Pipeline Metric: forwarder_critical_error_total with labels vertex, pipeline, vertex_type, replica and reason
MonoVertex Metric: mvtx_critical_error_total with labels mvtx_name, replica and reason

Testing

[codecov]

Codecov Report

❌ Patch coverage is 17.70833% with 79 lines in your changes missing coverage. Please review.
✅ Project coverage is 80.12%. Comparing base (58f8349) to head (291c17f).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
rust/numaflow-core/src/mapper/map/batch.rs	0.00%	17 Missing ⚠️
rust/numaflow-core/src/sinker/sink/user_defined.rs	0.00%	17 Missing ⚠️
rust/numaflow-core/src/transformer.rs	0.00%	17 Missing ⚠️
rust/numaflow-core/src/lib.rs	0.00%	15 Missing ⚠️
rust/numaflow-core/src/metrics.rs	56.66%	13 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3154      +/-   ##
==========================================
- Coverage   80.21%   80.12%   -0.10%     
==========================================
  Files         296      296              
  Lines       67530    67626      +96     
==========================================
+ Hits        54172    54188      +16     
- Misses      12805    12885      +80     
  Partials      553      553              

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[vigith]

perhaps we should try a macro approach.. let me try to do that in a follow up PR