[TRACKING] Improve container engine state handling

[incertum]

Motivation

We have identified a few areas of improvements wrt to state handling during the container lookup cycle, see #1595 (comment).

This issue serves to track progress in this regard.

It is also related to #291.

@gnosek @therealbobo @mstemm @leogr

[incertum]

Please also explore #1707: It's incorrect to initialize a lookup to SUCCESSFUL, by the way. I believe this is the strongest indication of a very suboptimal shared design across the container engines we support.

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[incertum]

/remove-lifecycle stale

Will get back to it soon.

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[leogr]

/remove-lifecycle stale

[incertum]

We didn't get to this for libs 0.18. We need a lot more time to improve this as it will also need lots of testing.

We can try libs 0.19 or the following dev cycle.

[FedeDP]

Agree!
/milestone 0.19.0

[FedeDP]

/milestone 0.20.0