CompatHelper: bump compat for ForwardDiff to 1, (keep existing compat)

[github-actions]

This pull request changes the compat entry for the ForwardDiff package from 0.10 to 0.10, 1.
This keeps the compat entries for earlier versions.

Note: I have not tested your package with this new compat entry.
It is your responsibility to make sure that your package tests pass before you merge this pull request.

[franckgaga]

@baggepinnen I'm working on removing PreallocationTools dependancy. The only place that I still use it is in RungeKutta, but I can avoid it by passing the $\mathbf{k}_1$ to $\mathbf{k}_4$ vectors in arguments and fill them in-place. I'll finish this today probably. Afterward, the conflict above will be resolved.

edit: FYI, I will concatenate $\mathbf{k}_1$ to $\mathbf{k}_4$ in a single $\mathbf{k}$ vector. First, it is more agnostic of the ODE solver. Second, the signature of state update function is way shorter like that.

[franckgaga]

Ok the test pass without the force_latest_compatible_version=true option. This option is not used for normal PRs, only CompatHelper automated PRs. I tried to resolved the conflicts in the compat entries, and also understand why this option is forced, but I may be too dumb for this XD. I will merge the PR anyway since I'm pretty confident that this is not caused by the changed in ForwardDiff.jl, and all the tests should pass in a normal CI runs (they pass locally).