[POA-3109] Handle panic while stopping apidump process while daemonset exit

[mudit-postman]

This pull request includes changes to prevent the agent from going into a panic state while closing the apidump process during the daemonset process shutdown and other changes.

Problem:

• Before changing the state of the apidump process to the final state and then calling the StopApiDumpProcess, we are checking if the process is already in the final state to avoid StopApiDumpProcess being called multiple times.
• But this final state check is not sync, due to which dirty read issue can happen and StopApiDumpProcess can be called multiple times which will send signal to already stopped channel hence causing program to go to panic state.

Changes:

Improvements to state handling:

• Added a check in changePodTrafficMonitorState to prevent state changes if the pod is already in a final state.
• Ensure the stop channel is closed only after the API dump process is stopped/exited.
• Removed redundant checks for end states in various methods, as these are now handled by the new state check in changePodTrafficMonitorState.

Other naming changes:

• Renamed StopApiDumpProcess to SignalApiDumpProcessToStop for better clarity on its purpose.
• Renamed isEndState to isTrafficMonitoringInFinalState for better readability and consistency.