Minor SwerveWithPathPlanner example improvements

[mjansen4857]

Fixes a minor issue with the example as well as adds a couple comments to hopefully avoid confusion

• Removes the set loop time of 0.004s. This should be the period at which the command scheduler is run, which does not appear to be changed in this example.
• Adds TODO comments to the max module speed and drive base radius config fields to make it more clear that these need to be changed. If left at 1, the robot would pretty much never rotate.

[jasondaming]

The base odometry update period for CommandSwerveDrivetrain is 250 times per second or 4ms. There may be a change in the future that detects if you have a Canivoire or not (Canivoire can handle this speed the RIO fails pretty miserably) and scales this back to 50 if not (it should also adjust this parameter).

So it won't use the faster odometry if the scheduler isn't also run faster?

[mjansen4857]

Yeah, but the period in HolonomicPathFollowerConfig needs to be the command scheduler period, otherwise the PID controllers will be broken if using anything other than just a P term. Even if odometry is being run at 250Hz, the command is still running at 50.