Installation blocks apt due to automatic initialization

[WoLpH]

While I understand that it could be useful to automatically initialize the database upon installation, on a large system this will result in your "apt install" stalling for minutes/hours.

I had to kill the updatedb command from a separate terminal to be able to use apt again.

Little excerpt from the installation:

```
Fetched 129 kB in 0s (612 kB/s)
(Reading database ... 153622 files and directories currently installed.)
Removing debian-archive-keyring (2021.1.1ubuntu2) ...
Selecting previously unselected package plocate.
(Reading database ... 153607 files and directories currently installed.)
Preparing to unpack .../plocate_1.1.15-1ubuntu2_amd64.deb ...
Unpacking plocate (1.1.15-1ubuntu2) ...
Setting up plocate (1.1.15-1ubuntu2) ...
update-alternatives: using /usr/bin/plocate to provide /usr/bin/locate (locate) in auto mode
Adding group `plocate' (GID 126) ...
Done.
Initializing plocate database; this may take some time...

Terminated
done
```

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jon (jmole)]

+1, please fix - no need to run the scan just to install.

[Jon Crall (erotemic)]

This is causing me issues. I installed mlocate in 22.04 (and from what I understand that is an alias for plocate), but it is taking too long, and I would rather just install other packages, but the dpkg lock is now in use, and stopping the install seems to break things, so without knowledge on how to stop this indexing gracefully I'm stuck waiting for updatedb to index my entire 20TB data drive before I can use anything else that needs the dpkg lock.