Allow touch_pad_filter_delete() after touch_pad_filter_stop() (IDFGH-9371)

[robot-controller]

Currently, when calling touch_pad_filter_delete() after touch_pad_filter_stop(), touch_pad_filter_delete fails because it tries to stop the timer again (which already happened in touch_pad_filter_stop()).

There might be situations in which the filter is stopped at some point in the code, but not deleted. If it is decided only at a later point that it can be deleted, this is not possible using touch_pad_filter_delete() anymore.

The proposed change consists of a simple check using esp_timer_is_active() if the timer needs to be stopped. If it does, it will be stopped, if it does not, this step will be skipped, avoiding an error and allowing to delete the timer.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[Alvin1Zhang]

Thanks for your contribution.