[INLONG-69] TubeMQ needs to provide API to cleanup consume group register info.

[dockerzhang]

Currently, TubeMQ maintains consume group information through the client's active unregister and registration timeout mechanism on the master side. If the client in the consume group or consume group quits unexpectedly without logging out, the consume group or client needs to wait for the server to time out before re-registering successfully. Can an API interface be provided to allow clients to clean up expired consume registration information to facilitate rapid clients registration?

JIRA link - [INLONG-69] created by gosonzhang

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[github-actions]

This issue is stale because it has been open 60 days with no activity.

[github-actions]

This issue is stale because it has been open for 60 days with no activity.