Import of big data sets

## Steps to reproduce
1. Deploy MongoDB cluster, for example on LXD
2. Obtain connection URI
3. Install mongosh on host machine in case of LXD or copy your data set into juju unit
4. Using "charmed-mongodb.mongoimport" (from inside of juju unit) or mongoimport (from host machine) start import data
5. Periodically check free space on disk.

## Expected behavior
Import of 70 GB of data should not consume 500+GB of disk space

## Actual behavior
Disk space is being consumed very quickly. This most likely happens due to audit logs.
Log rotation and allowing users to opt out from audit logging should solve the problem

## Versions
stable/164

Operating system:

Juju CLI:

Juju agent:

Charm revision:

LXD:

## Log output

Juju debug log:

## Additional context

Start by reproducing the 70 GB import with the MongoDB cluster and inspect disk usage and audit logs during the import. Done means the import no longer causes 500+ GB of disk consumption and the proposed log-rotation or audit-logging behavior is verified.

Written by the indexing model from the issue text.