1. RoundRectangle.GetPath() should not do ANY comepnsation for StrokeThickness
   because our callers do that for us. All we need to do is draw the rounded
   rectangle path using the width and height as-is.
2. RoundedRectangle.GetInnerPath() needs to be consistent about using the
   strokeThickness argument instead of (sometimes) using the StrokeThickness
   property which *may* be different. e.g. MauiDrawable.Android.cs's _shape's
   StrokeThickness is always 1 even when that is not the StrokeThickness that
   has been set on the Border).
3. MauiDrawable.Android.cs MUST pass a bounds argument to _shape?.ToPlatform()
   because that's what is expected if we want the stroke path (which we do,
   despite the 'clipPath' name suggesting otherwise).
4. MauiDrawable.Android.cs's _strokeThickness, _width, and _height member
   variables have already been multiplied by the pixel density on the Android
   device, so we must divide by _density to get back "MAUI pixels" that
   the RoundRectangle logic needs.
5. ContentViewGroup *also* needs to divide width and height by the pixel density
   instead of multiplying the StrokeThickness by the pixel density because
   clipShape.ToPlatform() calls RoundRectangle.InnerPathForBounds() which expects
   "MAUI pixels" rather than Android pixel coordinates.
6. ShapeExtensions.ToPlatform() now requires a 'float density` argument that
   represents the Android device's pixel density so that it can scale the
   "MAUI pixels" to "Android pixels".
7. I suspect that BorderDrawable.cs also needs to do this, but I'm not sure
   how to test that theory.