Added missing getHostElement to exposed exports as ɵgetHostElement

[SanderElias]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
• 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?
No change, just adding a missing export.

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• angular.io application / infrastructure changes
• Other... Please describe:

What is the current behavior?

render3 doesn't expose its public getHostElement.

What is the new behavior?

Its now exposed

Does this PR introduce a breaking change?

• Yes
• [x ] No

[ngbot]

I see that you just added the PR action: merge label, but the following checks are still failing:
     status "buildkite/angular" is failing
     status "google3" is pending
     status "ci/circleci: aio_preview" is pending
     status "ci/circleci: lint" is pending
     status "ci/circleci: test" is pending
     status "ci/circleci: build-packages-dist" is pending
     status "ci/circleci: test_ivy_aot" is pending
     status "ci/circleci: test_aio" is pending
     status "ci/angular: size" is pending
     status "continuous-integration/travis-ci/pr" is pending

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.

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