Improper lock usage leads to inode overflow in LockLocalStorage implementation

## Summary

Behaviour of [fasteners.InterProcessLock](https://github.com/harlowja/fasteners/blob/06c3f06cab4e135b8d921932019a231c180eb9f4/fasteners/process_lock.py#L114) is pretty weird: class creates a lockfile by provided path, if it doesn't exist, but not manage to remove it after lock is released.

It may lead to **uncontrolled lockfiles spam** in `/tmp` folder just because libcloud local driver is not removing [this lockfile](https://github.com/apache/libcloud/blob/trunk/libcloud/storage/drivers/local.py#L85) either.

## Detailed Information

This issue encountered in cassandra-medusa `v0.15` and lower, which was using `apache-libcloud<3.4.0,>=3.3.0` as a dependency.

Please see https://github.com/thelastpickle/cassandra-medusa/issues/528 for more details.

---

Seems like the lightweight fix is to run

```python
with contextlib.suppress(FileNotFoundError):
os.remove(filename)
```

just right in the [exit method](https://github.com/apache/libcloud/blob/trunk/libcloud/storage/drivers/local.py#L114).

Iniziare da libcloud/storage/drivers/local.py, nel metodo exit del driver locale, e verificare come viene gestito il nome del file di lock dopo che InterProcessLock lo rilascia. Confermare il comportamento con un test mirato o una riproduzione, quindi verificare che i file di lock rilasciati non rimangano più in /tmp senza influire sulla pulizia dei file mancanti.

Scritto dal modello di indicizzazione a partire dal testo della issue.