Dependencies utilized via vaadin-dev should be shaded into custom namespace

[mstahv]

Describe your motivation

vaadin-dev mode brings in dependencies that are not available during production deployments. Especially the commonly used ones may be rather confusing during the upgrades as they are still "OK" by IDE and build tools as they are now declared optional (and runtime dependencies to the same artifacts were dropped in the V25 cleanup).

Example code:

@Route
public class MainView extends VerticalLayout {

    public MainView() {
        // Basic SB + Vaadin 25.0.0-rc2
        add(org.apache.commons.lang3.StringUtils.capitalize("This works in dev mode only"));
    }
}

The most problematic ones highlighted here:

Additional context

Copilot is already shading at least one of the same deps.

[knoobie]

Fun Fact from my migration attempts: that's why I first did a clean build without vaadin-dev in my pom to ensure I didn't miss anything. Since it's quite common to just use those Utils classes without knowing where these came from

Edit: just to say it.. it is a huge benefit that vaadin-core does not need them anymore

[mstahv]

Yeah, bad habit to use them without re-declaring, but that's what we are like 🤷‍♂️

[mstahv]

Based on the blind trial we are using that bad habit in the core modules as well, quite many test modules didn't declare they used commons-io and friends... 😬 Claude curently fixing the dependencies...