docs: update stackblitz code version by fixing name of <live-example>

[ShubhankarKG]

The previous life example had the name "...-v0". This caused the products.ts in the tutorial to not have an id field.
Later on, during navigation, readers had to deduce that they need to add an id field manually.

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
• Documentation content changes
• angular.io application / infrastructure changes
• Other... Please describe:

What is the current behavior?

Issue Number: #40280

What is the new behavior?

The <live-example> points to the new products.ts file that has id for each product.

Does this PR introduce a breaking change?

• Yes
• No

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[ShubhankarKG]

@googlebot I signed it!

[mary-poppins]

You can preview c883e08 at https://pr40284-c883e08.ngbuilds.io/.

[petebacondarwin]

I don't think it is quite right to change this link to point to the "final" application, since then there is nothing for people to do as they are following along with the tutorial.

Instead I think we should update the v0 example to contain what is needed at: https://github.com/angular/angular/tree/master/aio/content/examples/getting-started-v0

[ShubhankarKG]

Sorry about that, did not realize I had linked the final application. 😅

[mary-poppins]

You can preview 3ed4567 at https://pr40284-3ed4567.ngbuilds.io/.

[aikithoughts]

I'll approve, pending @petebacondarwin provides final approval here.

Reviewed-for: global-docs-approvers

[aikithoughts]

Is this change overlapping with PR 40197?

[ShubhankarKG]

Yes, looks like it. This change is a subset of #40197.

[petebacondarwin]

@ShubhankarKG - thanks for working on this PR but since it is a subset of #40197, which is about to be merged, I am going to go ahead and close this PR.

[ShubhankarKG]

Sure

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