New version: KiteSimulators v0.4.0

[JuliaRegistrator]

• Registering package: KiteSimulators
• Repository: https://github.com/aenarete/KiteSimulators.jl
• Created by: @ufechner7
• Version: v0.4.0
• Commit: e1fc2fb13eea7c3842d96864d488042b28115fa4
• Reviewed by: @ufechner7
• Reference: Register package aenarete/KiteSimulators.jl#1 (comment)
• Description: Simulators for kite power systems
• Release notes:

#### Changed
- the build script now only installs `matplotlib` if it is not yet installed on the system
- improved the example `joystick.jl` and its documentation
- bump KiteControllers to 0.2.10
- bump KiteModels to 0.6.6  
A new kite model (KPS4_3L) was added, that uses three winches at the ground to steer the kite.
The new variant (version 3) of the KPS4 kite model allows to define polars that do not depend on the steering input, which makes it easier to define new kites.
- bump KitePodModels to 0.3.3  
A simplified KitePodModel was added with a linear relationship between depower setting and depower angle, which makes it easier to define new KCUs.
#### Added
- a new, torque controlled winch model
- you can now define the diameter and the aerodynamic drag coefficient of the KCU
- plot `aerodynamics`
#### Fixed
- changes of the polars had no effect
- changes of ```max_steering``` had no effect
#### Braking
- the function `next_step!` now requires either the parameter `set_speed`, which replaces `v_ro`, or the parameter `set_torque`, depending on the question if you use the `AsynchGenerator` or `TorqueControlledWinch` in the settings
- the function `init_sim` has the new parameter `delta`. It should be between 0.0 and 0.03 and defines the pre-tension of the tether. The parameter `stiffness_factor` should be between 0.1 and 1.0 and not longer smaller than 0.1.
- the constructor `FPCSettings` now requires the named parameter `dt`
- the constructor `SystemStateControl` now requires the named parameter `u_d0` and `u_d`

[github-actions]

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. AutoMerge Guidelines are all met! ✅

Your new version registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round.

2. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.