Fix SurfaceView overflow in RESIZE_MODE_ZOOM

[yemirhan]

Summary

• Fixes SurfaceView overflow in AspectRatioFrameLayout when using RESIZE_MODE_ZOOM, which caused videos to overlap neighboring items in RecyclerView/LazyColumn
• Keeps the frame at parent-provided size while measuring children at zoomed size, centers oversized children, and clips overflow via canvas and RenderNode clipping

Details

When using RESIZE_MODE_ZOOM, AspectRatioFrameLayout previously expanded its own measured dimensions beyond parent bounds. SurfaceView's separate hardware surface extended past the frame, causing videos to visually overlap neighboring list items. TextureView was unaffected since it renders through the normal canvas pipeline.

Changes to AspectRatioFrameLayout.java:

1. onMeasure() — After measuring children at zoomed size, resets the frame's measured dimensions back to the original parent-constrained size via setMeasuredDimension()
2. onLayout() — Centers children whose measured size exceeds the frame for a symmetric center-crop effect. wrap_content children (buffering spinner, error text) are left untouched
3. dispatchDraw() — Clips the canvas to the frame's bounds. Combined with FrameLayout's default clipChildren=true, this also enables RenderNode-based clipping for SurfaceView on API 29+

Other resize modes (FIT, FILL, FIXED_WIDTH, FIXED_HEIGHT) are unaffected — all new logic is guarded by resizeMode == RESIZE_MODE_ZOOM.

Test plan

• Verified with two PlayerViews (both using RESIZE_MODE_ZOOM + SurfaceView) stacked vertically with a colored divider — videos no longer bleed past their bounds
• Verify other resize modes (FIT, FILL, FIXED_WIDTH, FIXED_HEIGHT) still work correctly
• Test on API < 29 devices for canvas-only clipping path

Fixes #1107

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.