GC should have some reaction on container removal event

[carpawell]

Node is able to track container removal but currently, it does nothing.

It could:

1. Mark object of just removed container for removal;
2. Change its behavior (do not replicate objs, do not send estimations for that cnr, etc)
3. Mark container as removed in the Metabase to prevent operation with the objects that are still stored but technically do not exist anymore
4. ...

/cc @realloc

[roman-khimov]

Looks like we have some cases like this on mainnet (slightly modified tool from #2491):

2023/08/15 09:00:37 read container 5bq36EJ27VWTyzWtyVaeXMBr339TSex5v3uJLwnjMM3w: status: code = 3072 message = container not found
2023/08/15 09:00:37 read container 2pWrCbvejFqLy1Z3jEYLyACVX6ZdhLudnFjt2Ct5HT1B: status: code = 3072 message = container not found
2023/08/15 09:00:37 read container 2pWrCbvejFqLy1Z3jEYLyACVX6ZdhLudnFjt2Ct5HT1B: status: code = 3072 message = container not found
2023/08/15 09:00:37 read container 2pkfDULFobUXxVw4NVvqNjbmUwZHKv7dwU32W8SatrLr: status: code = 3072 message = container not found
2023/08/15 09:00:37 read container 5bq36EJ27VWTyzWtyVaeXMBr339TSex5v3uJLwnjMM3w: status: code = 3072 message = container not found
2023/08/15 09:00:37 read container 5bq36EJ27VWTyzWtyVaeXMBr339TSex5v3uJLwnjMM3w: status: code = 3072 message = container not found
2023/08/15 09:00:37 read container 5qj8tUtmARpJNtfzX1PfF4u8vugqAdM29x3Sv31Qdr5X: status: code = 3072 message = container not found
2023/08/15 09:00:38 read container EShohP7bvDmVoTXo8Xg2MXcXgi5yw1zjSqrSrhEz17rv: status: code = 3072 message = container not found
2023/08/15 09:00:38 read container EShohP7bvDmVoTXo8Xg2MXcXgi5yw1zjSqrSrhEz17rv: status: code = 3072 message = container not found
2023/08/15 09:00:38 read container 5qj8tUtmARpJNtfzX1PfF4u8vugqAdM29x3Sv31Qdr5X: status: code = 3072 message = container not found
2023/08/15 09:00:38 read container 8y8BmXckTq2GikSQ6x5MKyj7jEb6uGRm2JmsWheWi9Fp: status: code = 3072 message = container not found