Talking about differences between Gazebo Classic and Gazebo (ignition) for aerial vehicles -
So Gazebo classic needed a lot of additional plugins and ROS packages that needed to be made in order to Aerial vehicles to be modelled properly. This is I think a main driver of why RotorS was created (CrazyS was just an extension of that project made for the Crazyflie).
With the creation of the new Gazebo (called Ignition a while ago), efforts where made to include those externally made plugins to be part of the standard system classes of Gazebo. These include:
- MulticopterVelocityControl A velocity controller for linear velocity and yaw rate control of multirotors based on Lee controller (suitable for Twist messages).
- MulticopterMotorModel To generate thrust based on spinning props on motor.
- Sensors like IMU, GPS, magnetometer, pressure sensor etc
- Important physical engines like wind effect and flight dynamics
Of the last two I don't know how much of the RotorS project was included here but perhaps they had an influence.
So for your first requirement, (1) the new Gazebo has support for a velocity control of your aerial vehicle. There is an example called quadcopter.sdf that you should be able to try this out.
For (2), no I don't think this is possible with Gazebo alone. You'll need interface this using ROS(2) packages for that that are able to generate this for the vehicle, like NAV2. Also take a look at this overview of Aerial Autonomy stacks that the aerial robotics ROS community group has made. There are also tutorials made by PX4 and Ardupilot (see this overview of autopilot suites).
All in all, to go back to your first request about the differences between the two Gazebos, if you are not used to working with either of them, choose to focus on the new one as support for Gazebo Classic will stop soon.
Just a disclaimer, I'm neither a maintainer of Gazebo or RotorS/CrazyS so I hope that I didn't say anything that is not correct.