docs(dialog): correct and add back resolve property

[karansapolia]

PR Checklist

Please check that your PR fulfills the following requirements:

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?
Changes docs. Corrects and adds back resolve property doc in the $mdDialog.show() parameters list.

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

What is the current behavior?

Currently the resolve property is not listed or described in the $mdDialog.show(optionsOrPreset) parameters documentation. Refer to issue #7400. But as suggested in comments, slight documentation correction was required for the property.

Issue Number:
#11159

What is the new behavior?

The documentation for the resolve property has been updated and added back.

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.

[karansapolia]

I signed it!

[googlebot]

CLAs look good, thanks!

[Splaktar]

Thank you for sending this PR!

I think that one minor change to the type will help make this more clear.

[Splaktar]

Let's change {object=} to {function=} to match the changes to the text.

[karansapolia]

Oops. Correcting it right away.

[karansapolia]

@Splaktar This was just a docs edit. Ideally build should not fail. Read from other PRs that there was a Travis CI outage last night affecting the tests.

[Splaktar]

Yep, don't worry about that test failure. Can you please squash your commits and update the commit message to have Closes #11159 on the last line?

[Splaktar]

LGTM once squashed and commit message updated.

[karansapolia]

👍 Squashed and commit message updated. Thank you for bearing with me.

[Splaktar]

No problem at all. I understand that we have some requirements and elements of our process that take some time to learn! Thank you for keeping with it and making the requested updates!