chore: remove all @internal to fix offline compile

[jelbourn]

R: @robertmesserle @hansl @kara
CC: @iveysaur @devversion

When the code generated by the angular compiler interacts with the component, it does so through its class's public API. If anything is missing from the .d.ts, it will be an error when a downstream application tries to compile.

Also fixes some errors with tab's use of ngIf

[hansl]

Did you just remove all of them or did you actrually only removed the ones that were harmful?

[jelbourn]

To elaborate, with this PR, anything that is not part of the public API is prefixed with an underscore. Some of those things may be actual private, and other are TypeScript "public" so that Angular itself can see them, but are not intended to be exposed to end developers.

[jelbourn]

@hansl All of them, because there were very, very few that were actually not a problem (just a few in grid-list). I'm saying it's better to completely forgo using @internal because it's too easy to introduce an error with it.

[jelbourn]

Also, anything marked with TODO: internal is something for us to eventually mark as "Looks public, but needs to be omitted from the API docs", such as ControlValueAccessor methods and lifecycle hooks.

[robertmesserle]

Why was this one changed?

[jelbourn]

@ContentChildren etc. also can't be private, since Angular itself needs to touch them

[hansl]

LGTM as well.

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