[Enhancement] Use Streaming Lists when available

[KiptoonKipkurui]

Description
This PR Addresses an issue of potential runaway usage of memory due to chucking of reported statuses while watching for Kubernetes resources. Kubernetes 1.27 introduces a WatchList feature still at the alpha stage that allows one to get statuses of objects being watched as a streaming list as opposed to current implementations that uses a list request first before a watch request. This is done by setting sendInitialEvents=true param in a watch request.
This PR fixes #221

Notes for Reviewers

Signed commits

• Yes, I signed my commits.

[KiptoonKipkurui]

Point to note, So this PR is against a branch of meshery where the original PR was made and Reverted to

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (master@1e21ae5). Click here to learn what that means.

Additional details and impacted files

@@           Coverage Diff            @@
##             master    #255   +/-   ##
========================================
  Coverage          ?   2.76%           
========================================
  Files             ?       6           
  Lines             ?     398           
  Branches          ?       0           
========================================
  Hits              ?      11           
  Misses            ?     386           
  Partials          ?       1           

Flag	Coverage Δ
unittests	2.76% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.

[leecalcote]

@KiptoonKipkurui did you toss in the towel here?

[KiptoonKipkurui]

@leecalcote no I hadn't, by my last commit I had resolved the pending issues by then and comments, it was just a matter merging if all was well from the maintainers side