Introduce Android AppCompat renderers for Entry, Editor and Label

[jfversluis]

Description of Change

Adds 3 copies of renderers for Entry, Editor and Label which now inherit from the AppCompat version of the Android counterpart as opposed to the non-AppCompat version that it is currently.

To ensure a safety switch these are copies of the existing renderers, the new renderers are the default, but with a flag you can revert back to the old renderers and behavior.

Issues Resolved

• fixes [Bug] [Android] Google Emoji Policy Violation #15245

API Changes

Added:

• public class EntryAppCompatRenderer : EntryRendererBase<FormsAppCompatEditText>
• public class EditorAppCompatRenderer : EditorRendererBase<FormsAppCompatEditText>
• public class LabelAppCompatRenderer : FormsAppCompatTextView
• public class FormsAppCompatTextView : AppCompatTextView
• public class FormsAppCompatEditText : FormsAppCompatEditTextBase
• public class FormsAppCompatEditTextBase : AppCompatEditText
• public class FormsAppCompatEditText : FormsAppCompatEditTextBase
• public class FormsAppCompatEditTextBase : AppCompatEditText

Platforms Affected

• Android

Behavioral/Visual Changes

Hopefully none, but this should maximize backwards and forwards compatibility on Android for Entry, Editor and Label.

The new AppCompat renderers are the default as we expect no issues, but in case we do find issues, there is a flag to revert to the old behavior.

To do this, in your MainActivity.cs on Android call Forms.SetFlags("DisableAppCompatRenderers"); before the Forms.Init() call.

Before/After Screenshots

Not applicable

Testing Procedure

Add the resulting NuGet from this PR to your app and see if it behaves as before

PR Checklist

• Targets the correct branch
• Tests are passing (or failures are unrelated)