A caller can mostly already do this via forEach(), but having a specific method is faster (since the code does not need to read the value) and easier to use. The semantics of this method (e.g., ignore ENOENT while deleting a key, but throw on any other error) match those of the native BpfMap::clear method. Test: new unit tests Change-Id: I5cd32efd0f87c823cd2d0a2fa3a95a83093fb6f9