Fallback to Material 2 OutlinedButton on API 22

[seadowg]

Closes #5582

The problem was also now visible for the buttons shown in the quit form dialog so we wanted to see if there was anything quick we could do to fix it.

Why is this the best possible solution? Were any other approaches considered?

I've checked the problem on master and, as I hoped, the problem is fixed there (most likely because we're using a Material 3 theme and the latest Material Components version). We don't want to make that level of change for v2023.3 though - I've made it so that the buttons fallback to using the Material 2 OutlinedButton style for API < 22. This doesn't look amazing, but it's far better than not being able to read the text in the button.

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

Should just fix the issue. It'd be good to have a quick hunt for any other unreadable buttons/controls.

Before submitting this PR, please make sure you have:

• added or modified tests for any new or changed behavior
• run ./gradlew checkAll and confirmed all checks still pass OR confirm CircleCI build passes and run ./gradlew connectedDebugAndroidTest locally.
• added a comment above any new strings describing it for translators
• verified that any code or assets from external sources are properly credited in comments and/or in the about file.
• verified that any new UI elements use theme colors. UI Components Style guidelines