refactor(core): allow ElementRef in RippleRenderer.setupTriggerEvents

[crisbeto]

The way the RippleRenderer is set up at the moment is inconsistent from an API standpoint, because the constructor only accepts an ElementRef, whereas setupTriggerEvents only accepts an HTMLElement, and in most cases they're referring to the same DOM node. These changes make the two code paths consistent with each other by allowing HTMLElement | ElementRef<HTMLElement> in both of them.

[jelbourn]

LGTM

[ngbot]

I see that you just added the pr: merge ready label, but the following checks are still failing:
     status "ci/circleci: tests_browserstack" is failing

If you want your PR to be merged, it has to pass all the CI checks.

If you can't get the PR to a green state due to flakes or broken master, please try rebasing to master and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

[devversion]

I'm (personally) not really a fan of supporting both cases, as an experienced consumer of RippleRenderer should be able to retrieve the native element from the ElementRef, but yeah.. in favor of consistency this makes sense.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}