fix(toast): update style direction to flex-direction

[ypislon]

In the component md-toast the property "direction" is set to "row". It seems like it's intended to use "flex-direction", as "row" is not a valid value for the property direction, which should indicate the direction of text.

This doesn't change the behaviour of md-toast, just cleaning up a small typo :)

PR Type

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

The css property "direction" is set to the value of "row" in the md-toast component.

What is the new behavior?

In the component md-toast the property "direction" is set to "row". It seems like it's intended to use "flex-direction" instead of "direction", as "row" is not a valid value for the property direction, which should indicate the direction of text.

This doesn't change the behaviour of md-toast, just cleaning up a small typo :)

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[googlebot]

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 (e.g. 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 project maintainer to go/cla#troubleshoot.
• 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.

[ypislon]

I signed the CLA.

[googlebot]

CLAs look good, thanks!

[Splaktar]

Yep, looks like only rtl and ltr are valid values other than initial/inherit/unset.

[Splaktar]

Thank you for your contribution! Please update your commit message to follow the commit message guidelines. This is important for your changes to properly show up in the changelog.

For example: fix(toast): update style direction to flex-direction

[Splaktar]

Please update the commit message.

[Splaktar]

This looks good to me once the commit message gets updated. Thank you!

[ypislon]

Commit message is updated!

[Splaktar]

LGTM