feat: Add option for automatic timestep computation in wave solvers

[acitrain]

This PR add the possibility of compute automatically the timestep for wave propagation solvers.

How to use it?

• You add the correct switch in your XML (timestepStabilityLimit=1)
• You launch GEOS
• If the requested dt for the solver (forceDt) is higher than the CFL condition limit, substeps are used to remain below the condition
  Also, an option is added to input source wavelets using TableFunctions, with the option sourceWaveletTableNames
  There also a routine inside the PR to be wrapped using Pygeosx

[rrsettgast]

Shouldn't this always be used unless forceDt is set?

[acitrain]

In fact in this PR we are closer to the logic of the non-linear solvers: if you put a forceDt too big for the CFL condition the internal loop of the solver will do sub-steps to respect the CFL condition.
We decided to put this feature as an option to let the user be able to tests some dt on is own without getting into that routine.

[CusiniM]

I have approved it but two things about this PR:

1. please don't put PRs in the merge queue until they have all codeowners approvals.
2. IMO, the idea of forceDt is for the timestep size to be fixed. To let the solver adjust the timestep size one can just set a maxTiimestep size for the event instead of forcing it. So, I would argue that, if the forceDt is too large it's fine for the simulation to fail instead of substepping. I know that solver base sort of does this too but we have talked about removing it coz it is actually a lot easier to let the EventManager be the only object managing timestepping.