feat(core): support metadata reflection for native class types

[vicb]

closes #21731

supersedes #22315 (rebased version).

Original PR has all required approval for merging.

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this State. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

[ngbot]

I see that you just added the PR action: merge label, but the following checks are still failing:
     missing required labels: "PR target: *", "cla: yes"
     forbidden label detected: cla: no
     status "cla/google" is failing
     status "code-review/pullapprove" is pending
     status "ci/circleci: lint" is pending
     status "ci/circleci: build" 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.

[mary-poppins]

You can preview d7f7583 at https://pr22356-d7f7583.ngbuilds.io/.

[mary-poppins]

You can preview ee11579 at https://pr22356-ee11579.ngbuilds.io/.

[trotyl]

Just got that base class doesn't have to be an IdentifierName but whatever expression, for example a webpack dev build would generate:

class Derived extends _some__WEBPACK_IMPORTED_MODULE_1__["Base"] {
    constructor() {
        super(...arguments);
    }
}

And this won't work then. But should be OK for production in favor of scope hoisting.

Seems this check should be deprecated as per #22642 comes, I'm not sure whether it should be fixed.

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