Bugfix: Font Family resolving in Release Builds

[jreehuis]

Issue

MdcTheme does not pick up a font family which is specified in the Android Resource XML when using the release build type of the App.

MdcTheme expects the font file path in the APK to be res/font*<filename>. Optimizations to the App APK in release build types changes them to be res/[A-Z]{2}.<fileending>.
As the font family does not gets recognized in this situation the theme uses the current font family of MaterialTheme.

Fix

This PR changes the exptected APK font file path to res/*<filename>.

How to Test

The issue can be reproduced when building the sample app with the release build type from commit ba80854 . The Headline 3 does not get styled with Dancing Script as font family here.

Building the sample app with the releasebuild type from the PR head commit will style the headline 3 with the Dancing Script font family.

[google-cla]

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

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[google-cla]

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

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[jreehuis]

@googlebot I signed it!

[ricknout]

Thanks for the contribution! In addition to the sample, would it be possible to also add a font family to resources used by MdcThemeTest?

cc @chrisbanes as this might need to also be done in Accompanist AppCompat Theme Adapter

[jreehuis]

@ricknout Good point to actually test the XML font family parsing aswell. I adjusted the existing tests accordingly.