Make double disposal and double creation visible.

[polina-c]

Right now leak_tracker ignores cases of double disposal or double start of tracking.
It is possible for leak tracker to expose the issue as one more type of memory issue, in addition to notDisposed or not GCed types of memory leaks.

This issue is created to collect community feedback.

Please, upvote and add comment about your usage story, if you are interested.

[polina-c]

Not all users of leak_tracker want leak_tracker to fail on double dispatch of creation or disposal.
So, there should be an option to configure leak_tracker to fail or not to fail in such cases.

But there is a challenge: some dependencies may be doing double disposal that will cause failure of consumers that want to fail on double disposal.

May be it is better to implement in leak tracker instrumentation macro: flutter/flutter#137435