altos: Adjust flight algorithm to handle accel-only timer products
Make our accel-only product (easytimer) follow a shortend flight
state sequence:
1) startup Average samples
2.1) startup -> idle. Defined axis accel indicates not pointing up
2.2) startup -> pad. Defined axes accel indicates pointing up
3) pad -> boost. Accel > 20m/s² and speed > 5m/s
4) boost -> coast. accel < -2.5m/s² or 15 second boost
5.1) coast -> boost. average accel > 20m/s²
5.2) coast -> landed. All three accel axes stable for 10 seconds (< 2m/s² accel change)
Signed-off-by: Keith Packard <keithp@keithp.com>