[FIX] Docs: Registering Root Tasks - Incorrect/Unclear example

[nickfujita]

Description

Updates example for adding a root task, and calling it along with the other package level tasks.

Testing Instructions

Review options listed in issue #8972, and confirm this is the correct implementation of this example.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

6 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
examples-basic-web	⬜️ Ignored (Inspect)	Visit Preview		Aug 9, 2024 2:23pm
examples-designsystem-docs	⬜️ Ignored (Inspect)	Visit Preview		Aug 9, 2024 2:23pm
examples-native-web	⬜️ Ignored (Inspect)	Visit Preview		Aug 9, 2024 2:23pm
examples-svelte-web	⬜️ Ignored (Inspect)	Visit Preview		Aug 9, 2024 2:23pm
examples-tailwind-web	⬜️ Ignored (Inspect)	Visit Preview		Aug 9, 2024 2:23pm
examples-vite-web	⬜️ Ignored (Inspect)	Visit Preview		Aug 9, 2024 2:23pm

[vercel]

@nickfujita is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.

[anthonyshew]

This is a great observation. I'm thinking we should write both of the options you've described into the docs for thoroughness. Would you be up to adding an example of both?

Warning: It's highly likely that I'll be obnoxiously nitpicky about this, because I really like to make sure that we use succinct, excellent language when we're presenting folks with options. If you're ready for me to be mildly annoying about the precise way this gets written, we can keep going on this PR. Otherwise, I can take this on myself in a separate PR so I can be as surgical as I'd like to be without annoying you. 😄

[nickfujita]

Thanks @anthonyshew
Closing in favor of #9098