couch_index_compactor errors after migration to 3.3.2

Hi
After migration to 3.3.2 each time we shut down couchdb we get plenty of following errors.

`[error] 2023-11-13T11:16:52.821626Z couchdb@xxxxxxx <0.6820.1> -------- CRASH REPORT Process (<0.6820.1>) with 0 neighbors exited with reason: killed at gen_server:decode_msg/9(line:481) <= proc_lib:init_p_do_apply/3(line:226); initial_call: {couch_index_compactor,init,['Argument__1']}, ancestors: [<0.6809.1>,<0.6808.1>], message_queue_len: 0, links: [], dictionary: [], trap_exit: true, status: running, heap_size: 987, stack_size: 28, reductions: 463
[error] 2023-11-13T11:16:52.821822Z couchdb@xxxxxxxxx <0.6820.1> -------- CRASH REPORT Process (<0.6820.1>) with 0 neighbors exited with reason: killed at gen_server:decode_msg/9(line:481) <= proc_lib:init_p_do_apply/3(line:226); initial_call: {couch_index_compactor,init,['Argument__1']}, ancestors: [<0.6809.1>,<0.6808.1>], message_queue_len: 0, links: [], dictionary: [], trap_exit: true, status: running, heap_size: 987, stack_size: 28, reductions: 463
error] 2023-11-13T11:16:52.825666Z couchdb@xxxxxxxxxx <0.25628.0> -------- gen_server <0.25628.0> terminated with reason: killed
last msg: redacted
state: {st,<0.25619.0>,couch_mrview_index,undefined}
extra: []
[error] 2023-11-13T11:16:52.825822Z couchdb@xxxxxxxxx <0.25628.0> -------- gen_server <0.25628.0> terminated with reason: killed
last msg: redacted
state: {st,<0.25619.0>,couch_mrview_index,undefined}
extra: []`

Is this something we should worry about?

How we could fix those?

Thank you for the awesome work done on the new version!

[NOTE]: # ( ^^ Provide a general summary of the issue in the title above. ^^ )

## Description

[NOTE]: # ( Describe the problem you're encountering. )
[TIP]: # ( Do NOT give us access or passwords to your actual CouchDB! )

## Steps to Reproduce

[NOTE]: # ( Include commands to reproduce, if possible. curl is preferred. )

## Expected Behaviour

[NOTE]: # ( Tell us what you expected to happen. )

## Your Environment

[TIP]: # ( Include as many relevant details about your environment as possible. )
[TIP]: # ( You can paste the output of curl http://YOUR-COUCHDB:5984/ here. )

* CouchDB version used:
* Browser name and version:
* Operating system and version:

## Additional Context

[TIP]: # ( Add any other context about the problem here. )

Start with the couch_index_compactor process named in the crash report and review what happens during CouchDB shutdown after migration to 3.3.2. Reproduce the shutdown if possible and inspect the reported gen_server termination and couch_mrview_index state. Done means identifying whether the errors are expected shutdown behavior or a reproducible migration bug, with a confirmed fix or explanation.

Written by the indexing model from the issue text.