changed slam launch file according to the comments for the PR #4211

[iOzcan1]

---

Basic Info

Info	I have followed the comments on PR #4211 to make the changes
Ticket(s) this addresses	#4211 #4202
Primary OS tested on	Ubuntu 22.04
Robotic platform tested on	Gazebo simulation, turtlebot3
Does this PR contain AI generated software?	No

---

Description of contribution in a few bullet points

Description of documentation updates required from your changes

---

Future work that may be required in bullet points

For Maintainers:

• Check that any new parameters added are updated in navigation.ros.org
• Check that any significant change is added to the migration guide
• Check that any new features OR changes to existing behaviors are reflected in the tuning guide
• Check that any new functions have Doxygen added
• Check that any new features have test coverage
• Check that any new plugins is added to the plugins page
• If BT Node, Additionally: add to BT's XML index of nodes for groot, BT package's readme table, and BT library lists

[mergify]

@iOzcan1, your PR has failed to build. Please check CI outputs and resolve issues.
You may need to rebase or pull in main due to API changes (or your contribution genuinely fails).

[SteveMacenski]

@iOzcan1 please fix the linting + DCO issues. You also need to rebase or pull in main to your PR to make CI turn over

[mergify]

@iOzcan1, your PR has failed to build. Please check CI outputs and resolve issues.
You may need to rebase or pull in main due to API changes (or your contribution genuinely fails).

[SteveMacenski]

Linter is still failing :( You can see the details in Actions or https://app.circleci.com/pipelines/github/ros-planning/navigation2/11451/workflows/7b699eb7-8951-4c0d-986c-190fa7c26176/jobs/35289/tests

[SteveMacenski]

Will fix and open a PR shortly to get this in. @iOzcan1 thanks for getting this started! Very appreciated, but just going to finish up the details so that your contribution gets into main sooner than later 😄