fix(platform-server): setup NoopAnimationsModule in ServerModule by d…

[vikerman]

…efault

This is so that server side rendering does not throw an exception when it encounters animations on the server side and does not need the user to explicitly setup NoopAnimationsModule in their app server module.

Fixes #15098, #14784.

Please check if the PR fulfills these 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)

What kind of change does this PR introduce? (check one with "x")

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

What is the current behavior? (You can also link to an open issue here)
Server side rendering throws an exception even when using NoopAnimationsModule from app server module. The NoopAnimationsModule uses the DomRenderer by default and has to be routed through the ServerRenderer.

What is the new behavior?
NoopAnimationsModule is hooked up into ServerModule so that user does not have to do it themselves

Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[X] No

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