It would be nice to have these world related ENV variables

### Enhancement Type

Improve an existing feature

### Describe the enhancement

Hey! Could you please add those new ENV variables?

- **COPY_WORLD_DEST** (String) -> Change the world copy destination, I like to use all the worlds inside a worlds directory, for organization and plugin development purposes, I'd like to set that variable to "/data/worlds" so it doesn't copy the worlds to the default "/data" location.

- **REMOVE_OLD_WORLDS** (Boolean) -> Wether or not clean up the worlds directory set with **COPY_WORLD_DEST** variable before copying the worlds on each startup, I'd like to use this feature on a minigame server, so the worlds get restored on each server restart.

- **REMOVE_OLD_WORLDS_INCLUDE** and **REMOVE_OLD_WORLDS_EXCLUDE** (String) -> Allow to include or exclude worlds when using **REMOVE_OLD_WORLDS** variable.

- **WORLDS** (String) -> List of worlds from "/worlds" that should be copied to the **COPY_WORLD_DEST** (taking into consideration **REMOVE_OLD_WORLDS**, **REMOVE_OLD_WORLDS_INCLUDE**, and **REMOVE_OLD_WORLDS_EXCLUDE** variables), with the possibility to copy all of them setting this to "*" OR "ALL". This variable could be also merged into the existing **WORLD** one, specifying multiple paths or "/worlds/*" to copy all of them.

Thanks!

Start by locating the startup logic that handles the existing WORLD variable and copies worlds from /worlds. Trace how destination selection, cleanup, and world filtering currently work, then verify the requested variables and their include/exclude behavior across startup scenarios.

Written by the indexing model from the issue text.