chore(examples): rename flask-ride-sharing-app in tutorial

[kolesnikovae]

In #3769 I renamed the flask-ride-sharing-app to ride-sharing-app to align with the shared README, where it is referred to in this way. However, in the KillerCoda tutorial, we're still using flask-ride-sharing-app. I'm updating the tutorial to reflect the new name and add a link to README.

[simonswine]

LGTM

Was not really aware of killercoda.com. I imagine we need to backport those PRs, in order to update the "latest" version of the docs.

[github-actions]

Hello @simonswine!
Backport pull requests need to be either:

• Pull requests which address bugs,
• Urgent fixes which need product approval, in order to get merged,
• Docs changes.

Please, if the current pull request addresses a bug fix, label it with the type/bug label.
If it already has the product approval, please add the product-approved label. For docs changes, please add the type/docs label.
If the pull request modifies CI behaviour, please add the type/ci label.
If none of the above applies, please consider removing the backport label and target the next major/minor release.
Thanks!

[github-actions]

Hello @simonswine!
Backport pull requests need to be either:

• Pull requests which address bugs,
• Urgent fixes which need product approval, in order to get merged,
• Docs changes.

Please, if the current pull request addresses a bug fix, label it with the type/bug label.
If it already has the product approval, please add the product-approved label. For docs changes, please add the type/docs label.
If the pull request modifies CI behaviour, please add the type/ci label.
If none of the above applies, please consider removing the backport label and target the next major/minor release.
Thanks!

[github-actions]

This PR must be merged before a backport PR will be created.

[github-actions]

The backport to release/v1.9 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-3778-to-release/v1.9 origin/release/v1.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 7ec96ae36b26e9cc404881c62986128557be71d6

When the conflicts are resolved, stage and commit the changes:

git add . && git cherry-pick --continue

If you have the GitHub CLI installed:

# Push the branch to GitHub:
git push --set-upstream origin backport-3778-to-release/v1.9
# Create the PR body template
PR_BODY=$(gh pr view 3778 --json body --template 'Backport 7ec96ae36b26e9cc404881c62986128557be71d6 from #3778{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title '[release/v1.9] chore(examples): rename flask-ride-sharing-app in tutorial' --body-file - --label 'type/docs' --label 'backport' --base release/v1.9 --milestone release/v1.9 --web

Or, if you don't have the GitHub CLI installed (we recommend you install it!):

# Push the branch to GitHub:
git push --set-upstream origin backport-3778-to-release/v1.9

# Create a pull request where the `base` branch is `release/v1.9` and the `compare`/`head` branch is `backport-3778-to-release/v1.9`.

# Remove the local backport branch
git switch main
git branch -D backport-3778-to-release/v1.9

[github-actions]

The backport to release/v1.10 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-3778-to-release/v1.10 origin/release/v1.10
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 7ec96ae36b26e9cc404881c62986128557be71d6

When the conflicts are resolved, stage and commit the changes:

git add . && git cherry-pick --continue

If you have the GitHub CLI installed:

# Push the branch to GitHub:
git push --set-upstream origin backport-3778-to-release/v1.10
# Create the PR body template
PR_BODY=$(gh pr view 3778 --json body --template 'Backport 7ec96ae36b26e9cc404881c62986128557be71d6 from #3778{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title '[release/v1.10] chore(examples): rename flask-ride-sharing-app in tutorial' --body-file - --label 'type/docs' --label 'backport' --base release/v1.10 --milestone release/v1.10 --web

Or, if you don't have the GitHub CLI installed (we recommend you install it!):

# Push the branch to GitHub:
git push --set-upstream origin backport-3778-to-release/v1.10

# Create a pull request where the `base` branch is `release/v1.10` and the `compare`/`head` branch is `backport-3778-to-release/v1.10`.

# Remove the local backport branch
git switch main
git branch -D backport-3778-to-release/v1.10