Add colab notebook for fine-tuning mT5 on XNLI

[mayhewsw]

This is basically copying the t5-trivia notebook from the T5 repo.

I've run this with mT5-small for a small number of steps (5700), and got the following validation accuracies.

INFO:absl:eval/xnli_dev_test.all_langs/accuracy at step 1005700: 65.673
INFO:absl:eval/xnli_dev_test.ar/accuracy at step 1005700: 62.610
INFO:absl:eval/xnli_dev_test.bg/accuracy at step 1005700: 68.956
INFO:absl:eval/xnli_dev_test.de/accuracy at step 1005700: 68.072
INFO:absl:eval/xnli_dev_test.el/accuracy at step 1005700: 67.671
INFO:absl:eval/xnli_dev_test.en/accuracy at step 1005700: 79.960
INFO:absl:eval/xnli_dev_test.es/accuracy at step 1005700: 72.129
INFO:absl:eval/xnli_dev_test.fr/accuracy at step 1005700: 69.157
INFO:absl:eval/xnli_dev_test.hi/accuracy at step 1005700: 61.446
INFO:absl:eval/xnli_dev_test.ru/accuracy at step 1005700: 67.309
INFO:absl:eval/xnli_dev_test.sw/accuracy at step 1005700: 55.422
INFO:absl:eval/xnli_dev_test.th/accuracy at step 1005700: 64.177
INFO:absl:eval/xnli_dev_test.tr/accuracy at step 1005700: 61.767
INFO:absl:eval/xnli_dev_test.ur/accuracy at step 1005700: 57.912
INFO:absl:eval/xnli_dev_test.vi/accuracy at step 1005700: 63.333
INFO:absl:eval/xnli_dev_test.zh/accuracy at step 1005700: 65.181

[google-cla[bot]]

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).

:memo: 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.

[mayhewsw]

@googlebot I signed it!

[lintingxue]

Hey Stephen, thanks for the suggestion, unfortunately we don't accept external PRs for this repo.