[docs-metrics] Remove predicate-based View examples

[reyang]

Most users got it wrong, and the error is not detected/reported at SDK initialization time (the exceptions simply got swallowed) which makes it a big pit of failures.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.55%. Comparing base (6250307) to head (c1214c4).
Report is 187 commits behind head on main.

❗ Current head c1214c4 differs from pull request most recent head b27340e. Consider uploading reports for the commit b27340e to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5554      +/-   ##
==========================================
+ Coverage   83.38%   85.55%   +2.17%     
==========================================
  Files         297      289       -8     
  Lines       12531    12493      -38     
==========================================
+ Hits        10449    10689     +240     
+ Misses       2082     1804     -278     

Flag	Coverage Δ
unittests	?
unittests-Solution-Experimental	85.57% <ø> (?)
unittests-Solution-Stable	85.47% <ø> (?)

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

see 77 files with indirect coverage changes

[cijothomas]

LGTM.

@alanwest Please review. We have discussed the potential pitfalls from View long ago!

[CodeBlanch]

Most users got it wrong

Will having less/no documentation help with that? If we don't want to show this most places I'm fine with that. But IMO we should have an advanced doc/section that at least calls out the potential pitfalls for anyone who chooses to use it.

[reyang]

Most users got it wrong

Will having less/no documentation help with that? If we don't want to show this most places I'm fine with that. But IMO we should have an advanced doc/section that at least calls out the potential pitfalls for anyone who chooses to use it.

I think that's the right direction. Eventually we might want to deprecate this API, and if there are good number of users who need certain feature, another better API might be introduced which doesn't have this callback pattern.