UdpCmdDemux: remove stop-"responsiveness" timer

I think it's best to remove the timer tick from UdpCommandDemuxer.
I looked at it again and it doesn't actually help with responsiveness.
Whatever it contributes is no different from what stop() does.
They both just call timer.cancel and cmdsocket.cancel.
So if that doesn't stop the socket in stop(), it won't magically
stop it more effectively if I call it from a timer handler.

commonLibs/livoxProto1/udpCommandDemuxer.h

@@ -3,7 +3,6 @@
 
 #include <atomic>
 #include <memory>
-#include <boost/asio/deadline_timer.hpp>
 #include <boost/asio/posix/stream_descriptor.hpp>
 #include <componentThread.h>
 
@@ -57,7 +56,6 @@ private:
 	void setupSocket();
 	void startAsyncReceive();
 	void onDataReady(const boost::system::error_code& error);
-	void onTimerTick(const boost::system::error_code& error);
 	void processIncomingData();
 
 	std::shared_ptr<smo::ComponentThread> componentThread;
@@ -66,7 +64,6 @@ private:
 
 	// Socket and async objects
 	std::shared_ptr<boost::asio::posix::stream_descriptor> cmdEndpointFdDesc;
-	boost::asio::deadline_timer timer;
 
 	// State management
 	std::atomic<bool> isActive{false};