Ros2 ign update rolling

[Darkproduct]

With Gazebo classic's EOL in January 2025 we should create a new ros2-classic branch and use Gazebo (former Ignition Gazebo) on the default ros2 one.

## TODO
- [ ] Create new branch ros2-classic from ros2
- [ ] Delete the ros2 branch
~~- [ ] Create new branch ros2 from ros2-ign ~~
- [ ] This PR should target the new ros2 branch

I'm not sure how long Ignition Gazebo will stay supported, so we should keep ros2-ign around until then.

What is done in this PR:

• Used the ros2-ign branch as starting point
• Followed the migration guide from Ignition
• Fixed the dependencies in the package.xml of the ros2-ign branch (should be cherry-picked there as well and maybe fixes Issue with rosdep with ros2  #74)
• Fixed a a lot of file permissions (should be cherry-picked as well)
• Changed the package type to python
• Removed hooks, use GZ_SIM_RESOURCE_PATH which is updated in simulation.launch.py
• Add new launch parameter verbose to increase Gazebo verbosity
• robot_spawner.launch.py is now more flexible with parameter overwrites and can also load models from file
• Updated old plugins
• Fix Found a few further issues or bugs while testing the configs. #45 out of bounds bug

[Rick-v-E]

Thanks!
I think it makes more sense to create a new branch ros2-gz for this update right? Because humble still needs to use ros2-ign. In that way, we don't mess up everyone that's checkout on the ros2-ign branch. However, I think it's good to make this new code the default branch for this repository and adapt the readme of the ros2 and main branch to indicate that they are deprecated.

[Darkproduct]

I'm not sure if I understand, here is what I suggest:

• Rename the current ros2 branch to ros2-classic because Gazebo classic is EOL anyway
• Make this PR the new ros2 branch
• ros2-ign will stay as it is, because as you said it is still needed on some supported versions

If this is fine with you, I can make the changes

[Rick-v-E]

I would keep the current ros2 branch and just add an additional ros2-gz branch, which we can make the default one. If someone clones the repository by git clone https://github.com/FieldRobotEvent/virtual_maize_field/ they automatically get the ros2-gz branch. Then everyone using the current ros2 branch can continue doing that without changing anything.

But if you think replacing the branch is better, I am ok with that.

[Darkproduct]

I also finally found the index out of bounds error which fixes #45 which is also included in #79

[Rick-v-E]

And probably add a file ros-rolling-gz-test.yaml to .github/workflows to automatically test branch:

# Rolling Ridley (June 2020 - )
name: ros-rolling

on:
  workflow_dispatch:
  pull_request:
    branches:
      - ros2-gz
  push:
    branches:
      - ros2-gz

jobs:
  build:
    runs-on: ubuntu-latest
    container:
      image: ubuntu:noble
    steps:
      - uses: ros-tooling/setup-ros@master
        with:
          required-ros-distributions: rolling
      - uses: ros-tooling/action-ros-ci@v0.3
        with:
          package-name: virtual_maize_field
          target-ros2-distro: rolling