[Improvement]: clean the resource when optimizer instance expired

[Yao-MR]

Search before asking

• I have searched in the issues and found no similar issues.

What would you like to be improved?

when release the optimizer, the amoro will remove the resource in the and then remove the instance

when the optimizer expired, the amoro will remove the instance and will not remove resouce in the db, which will cause this dirty data,

How should we improve?

we should flow the step when release the optimzier, when we detect the optimizer instance expired, not only should we remove the optimzier, we also should remove the resource record in the db

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Subtasks

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[majin1102]

Thanks for raising this issue.

Can you point out the influence of this improvement? or what have you encountered.
I think expiring and deleting are somehow different operation