Updates tutorials file extensions from .hbs to .gjs

---

Commit:  ember-learn/super-rentals-tutorial@ee27475
Script:  https://github.com/ember-learn/super-rentals-tutorial/blob/ee2747508b0384f5bf4fa927e639b6c5ba4f96eb/.github/workflows/build.yml
Logs:    https://github.com/ember-learn/super-rentals-tutorial/commit/ee2747508b0384f5bf4fa927e639b6c5ba4f96eb/checks

Author: ember-tomster

guides/release/tutorial/part-1/orientation.md

@@ -220,11 +220,12 @@ Build successful (9761ms)
 
 Slowest Nodes (totalTime >= 5%) | Total (avg)
 -+-
-Babel: @embroider/macros (1) | 406ms
+Babel: @embroider/macros (1) | 398ms
+Babel: ember-tracked-storage-polyfill (1) | 25ms
 
 
 
-  VITE v7.1.12  ready in 3849 ms
+  VITE v7.1.12  ready in 3923 ms
 
   ➜  Local:   http://localhost:4200/
 ```

guides/release/tutorial/part-1/reusable-components.md

@@ -101,11 +101,11 @@ Build successful (13286ms)
 
 Slowest Nodes (totalTime >= 5%) | Total (avg)
 -+-
-Babel: @embroider/macros (1) | 397ms
+Babel: @embroider/macros (1) | 423ms
 
 
 
-  VITE v7.1.12  ready in 3786 ms
+  VITE v7.1.12  ready in 3850 ms
 
   ➜  Local:   http://localhost:4200/
 ```

guides/release/tutorial/part-1/working-with-data.md

@@ -418,7 +418,7 @@ Awesome! Now we're in business.
 
 ## Loops and Local Variables in Templates with `{{#each}}`
 
-The last change we'll need to make is to our `index.hbs` route template, where we invoke our `<Rental>` components. Previously, we were passing in `@rental` as `@model` to our components. However, `@model` is no longer a single object, but rather, an array! So, we'll need to change this template to account for that.
+The last change we'll need to make is to our `index.gjs` route template, where we invoke our `<Rental>` components. Previously, we were passing in `@rental` as `@model` to our components. However, `@model` is no longer a single object, but rather, an array! So, we'll need to change this template to account for that.
 
 Let's see how.
 

guides/release/tutorial/part-2/provider-components.md

@@ -1,6 +1,6 @@
 <!-- Heads up! This is a generated file, do not edit directly. You can find the source at https://github.com/ember-learn/super-rentals-tutorial/blob/master/src/markdown/tutorial/part-2/12-provider-components.md -->
 
-In this chapter, we'll work on adding a new search feature, and refactor our `index.hbs` template into a new component along the way. We'll learn about a new pattern for passing data around between components, too! Once we're done, our page will look like this:
+In this chapter, we'll work on adding a new search feature, and refactor our `index.gjs` template into a new component along the way. We'll learn about a new pattern for passing data around between components, too! Once we're done, our page will look like this:
 
 <!-- TODO: make this a gif instead -->
 
@@ -58,7 +58,7 @@ Awesome, one step done. Now, this input looks great, but it doesn't actually _do
 
 In order to make our search box actually work, we are going to need to retain and store the text that the user types in when they use the search box. This text is the search query, and it is a piece of _[state](../../../components/component-state-and-actions/)_ that is going to change whenever the user types something into the search box.
 
-But where are we going to put this newly-introduced piece of state? In order to wire up the search box, we need a place to store the search query. At the moment, our search box lives on the `index.hbs` route template, which doesn't have a good place to store this search query state. Darn, this would be so much easier to do if we had a component, because we could just store the state directly on the component!
+But where are we going to put this newly-introduced piece of state? In order to wire up the search box, we need a place to store the search query. At the moment, our search box lives on the `index.gjs` route template, which doesn't have a good place to store this search query state. Darn, this would be so much easier to do if we had a component, because we could just store the state directly on the component!
 
 Wait...why don't we just refactor the search box into a component? Once we do that, this will all be a bit easier—hooray!