Added verified Dockerised workflows' instructions for running Interactive Web & Nav2 Integration demos

[cardboardcode]

New Feature Implementation 🌟

Implemented Feature(s) 📚

• Provided docker-specific build and run instructions in root README.md and nav2_integration/README.md.
• Created a verified Dockerfile.nav2 base image file under docker/ which includes the manual steps defined in Setup section of nav2_integration/README.md
• Surfaced link to Nav2 Integration Demonstration README.md in root README.md to make it more accessible and apparent for new users.

Implementation Description 💬

The docker-centric instructions complement the existing 2 build and run approaches, namely local and distrobox, in root README.md.

It is mainly catered to users who are more familiar with using just docker and to make explicit environment and configurations needed to allow GUI display for Nav2 Integration demonstration.

Note

Here's how the documentation looks like:

• https://github.com/cardboardcode/next_gen_prototype/tree/feature/dockerfile_nav2sim#1-install-ros-2-rust-and-colcon-cargo
• https://github.com/cardboardcode/next_gen_prototype/tree/feature/dockerfile_nav2sim/nav2_integration#docker-setup

GenAI Use

We follow OSRA's policy on GenAI tools

• I used a GenAI tool in this PR.
• I did not use GenAI ❌

[arjo129]

Thanks for this docker file! It makes sense to create a separate image for nav2 robots, however right now this docker file will essentially have exactly the same deps as our custom ros2_rust_base development image. This makes me wonder what value this current docker file adds. I do think packaging the nice project nicely is very important so we should think carefully about what "artifacts" we'd like exported.

(PS Id also recommend adding a CI workflow that actually builds any dockerfile that we produce otherwise it'll lead to random floating dockerfiles that are broken/untested later on down the line).

[cardboardcode]

Ah noted.

The original intent of this Dockerfile.nav2 is to automate the manual installation steps in Manual Setup of Nav2 Demo README.md so users need not have to do so.

Let me run the nav2 simulation with Dockerfile.base file shortly. If the simulation still runs as expected, I would probably have Dockerfile.nav2 removed in favour of less random floating dockerfiles.

Will also look into adding the CI workflow in a seperate PR. Will link here in the thread once available.

[cardboardcode]

Progress Update 💬

Managed to get nav2 integration demo working with just Dockerfile.base and a few proposed changes.

Will remove Dockerfile.nav2 for now.