Added extensions for padding and margins

[mercuriy94]

Convenient extensions for applying insets, helping to avoid boilerplate code

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

[mercuriy94]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[chrisbanes]

First up, thanks for the PR!

I'm currently thinking about holding off adding methods and functionality like this until we can use the new WindowInsets[Compat].Type values. The API is likely to change a lot once we can use Type.

applySystemWindowInsetsToPadding() then becomes applyInsetsToPadding(type: Int) and is much more flexible.

WDYT?

[chrisbanes]

Although we could merge this, and then deprecate later (in the re-write).

[mercuriy94]

Hello, yes, I agree!
We will have to change api in the future.
But I think that now it makes sense to adopt pr in order to give the opportunity to use convenient extenssions in current projects.
In the future, when the api changes, a new version will be released, but for those who use the old version, support will remain.

[chrisbanes]

Yeah, sounds good to me.