docs: update docs to use HttpClientModule instead of HttpModule

[agussman]

Updated most examples to use HttpClientModule instead of deprecated HttpModule

fix #19280

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?

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

What is the current behavior?

Issue Number: #19280

What is the new behavior?

Updated doc examples to use HttpClientModule instead of old HttpModule.

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

[ngbot]

Hi @agussman! This PR has merge conflicts due to recent upstream merges.
Please help to unblock it by resolving these conflicts. Thanks!

[ngbot]

Hi @agussman! This PR has merge conflicts due to recent upstream merges.
Please help to unblock it by resolving these conflicts. Thanks!

[ngbot]

Hi @agussman! This PR has merge conflicts due to recent upstream merges.
Please help to unblock it by resolving these conflicts. Thanks!

[jenniferfell]

@agussman : Hi. Now that v6 is released, we're getting around to closing some open loops. I apologize for letting this sit for so long. If you're still interested, we'd be thrilled to have you contribute this fix. It's a bit out-of-date, as I think some PRs were merged that fixed some of the HTTPModule issues you were addressing. I think, however, there are still some areas that aren't fixed. I made a few notes on the original issue.

Is there anything I can do to help you make this contribution? Thanks!

[agussman]

@jenniferfell : Yes, I would like to contribute the PR. What is required from my end?

[jenniferfell]

@agussman: Fantastic! The first thing I recommend doing is resolving conflicts between what we have in master and what you have in this PR. We just released v6 yesterday, so it's a good time. If you're familiar with github, there's nothing special about doing this with our example and doc files.

For some tips about how we merge changes from master into our doc-examples branches, my team started to collect some information:
https://github.com/ExpertSupport/doc-workflow/wiki/Daily-Startup (see step 2 especially)
https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/

[agussman]

Hi @jenniferfell : I merged in the latest master, resolved conflicts, and updated the PR. Can you take a look and let me know if there are any issues that would prevent it from being merged? Thanks!

[agussman]

@IgorMinar Thank you for the code review!

@jenniferfell Anything else needed from me?

[IgorMinar]

caretaker note: the failing CI tests seems like an unrelated flake. I restarted the job, but if that doesn't help please check on the failure and merge this PR.

@agussman I don't think so. I think the CI failure is unrelated to your change, so let's wait for the caretaker to investigate.

[vicb]

@agussman there is an issue with the changes causing the CI to fail. Could you please take a look.

[agussman]

@vicb: Happy to take a look, but per @IgorMinar's comment the CI failures don't appear to be related to these changes.

[gkalpak]

@agussman, there are still files that are importing from @angular/http (e.g. importing Http) and some of them are intentiinally doing so. You need to ensure that the examples e2e tests pass with any changes you make.

(We also nee to make sure that guide text is update (if necessary).)

[brandonroberts]

@agussman will you rebase on master?

[brandonroberts]

Closing in favor of smaller PRs already merged and in process

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