chore: added navigation in the kotlin sample app

[Shahroz16]

Complete each step to get your pull request merged in. Learn more about the workflow this project uses.

• [ ] Assign members of your team to review the pull request.
• [ ] Wait for pull request status checks to complete. If there are problems, fix them until you see that all status checks are passing.
• [ ] Wait until the pull request has been reviewed and approved by a teammate
• [ ] After pull request is approved, and you determine it's ready add the label "Ready to merge" to the pull request and it will automatically be merged.

[github-actions[bot]]

Pull request title looks good 👍!

If this pull request gets merged, it will not cause a new release of the software. Example: If this project's latest release version is 1.0.0. If this pull request gets merged in, the next release of this project will be 1.0.0. This pull request is not a breaking change.

All merged pull requests will eventually get deployed. But some types of pull requests will trigger a deployment (such as features and bug fixes) while some pull requests will wait to get deployed until a later time.

This project uses a special format for pull requests titles. Expand this section to learn more (expand by clicking the ᐅ symbol on the left side of this sentence)...

This project uses a special format for pull requests titles. Don't worry, it's easy! This pull request title should be in this format: ``` : short description of change being made ``` **If your pull request [introduces breaking changes](https://web.archive.org/web/20220725195319/https://nordicapis.com/what-are-breaking-changes-and-how-do-you-avoid-them/)** to the code, use this format: ``` !: short description of breaking change ``` where `` is one of the following: - `feat:` - A feature is being added or modified by this pull request. Use this if you made any changes to any of the features of the project. - `fix:` - A bug is being fixed by this pull request. Use this if you made any fixes to bugs in the project. - `docs:` - This pull request is making documentation changes, only. - `refactor:` - A change was made that doesn't fix a bug or add a feature. - `test:` - Adds missing tests or fixes broken tests. - `style:` - Changes that do not effect the code (whitespace, linting, formatting, semi-colons, etc) - `perf:` - Changes improve performance of the code. - `build:` - Changes to the build system (maven, npm, gulp, etc) - `ci:` - Changes to the CI build system (Travis, GitHub Actions, Circle, etc) - `chore:` - Other changes to project that don't modify source code or test files. - `revert:` - Reverts a previous commit that was made. ### Examples: ``` feat: edit profile photo refactor!: remove deprecated v1 endpoints build: update npm dependencies style: run formatter ``` Need more examples? Want to learn more about this format? [Check out the official docs](https://www.conventionalcommits.org/). **Note:** If your pull request does multiple things such as adding a feature _and_ makes changes to the CI server _and_ fixes some bugs then you might want to consider splitting this pull request up into multiple smaller pull requests.

[codecov[bot]]

Codecov Report

Merging #196 (02a11a5) into main (914f1b7) will not change coverage. The diff coverage is n/a.

@@            Coverage Diff            @@
##               main     #196   +/-   ##
=========================================
  Coverage     62.77%   62.77%           
  Complexity      218      218           
=========================================
  Files            91       91           
  Lines          2090     2090           
  Branches        270      270           
=========================================
  Hits           1312     1312           
  Misses          675      675           
  Partials        103      103           

[github-actions[bot]]

Build available to test Version: shahroz-kotlin-sample-app-navigation-SNAPSHOT Repository: https://s01.oss.sonatype.org/content/repositories/snapshots/