📝 Description

Optimize model monitoring stream pod, avoiding working on duplicate events in TSDB steps

🛠️ Changes Made

This change includes:

1. Splitting the graph earlier between parquet to tsdb branches, avoiding flatten for events that target to the TSDB
2. Small change in the handling of NOP event
3. Mapping the first event of batch to the TSDB while this event hold all necessary data
4. v3io - include events table, added a MapFeatureNamesTSDB for some fields need to be covered

TDEngine and TimeScaleDB:

V3io:

✅ Checklist

• I updated the documentation (if applicable)
• I have tested the changes in this PR
• I confirmed whether my changes are covered by system tests
  • If yes, I ran all relevant system tests and ensured they passed before submitting this PR
  • I updated existing system tests and/or added new ones if needed to cover my changes
• If I introduced a deprecation:
  • I followed the Deprecation Guidelines
  • I updated the relevant Jira ticket for documentation

🧪 Testing

Manual for v3io and TimeScaleDB, test_app_flow with ModelRunnerStep using both v3io and TimeScaleDB TSDB

🔗 References

• Ticket link: https://iguazio.atlassian.net/browse/ML-11639 , https://iguazio.atlassian.net/browse/ML-9667
• Design docs links:
• External links:

🚨 Breaking Changes?

• Yes (explain below)
• No

🔍️ Additional Notes