Set table fallback classes in bootstrap instead of relying on app template to do it

[LordSimal]

Description

Till now we had the following in all our app templates

if (PHP_SAPI !== 'cli') {
    FactoryLocator::add('Table', (new TableLocator())->allowFallbackClass(false));
}

but to clean this up (and don't make users questions why this kind of weird code is in the app template) we could move this to the bootstrap hook of the plugin via just adding

// We need fallback classes for baking code
FactoryLocator::add('Table', (new TableLocator())->allowFallbackClass(true));

[nicosp]

An alternative is to set the table locator only in the BakeCommand like:

public function initialize(): void
{
    parent::initialize();

    $locator = new TableLocator();
    $locator->allowFallbackClass(true);
    $this->setTableLocator($locator);
}

This isolates the locator inside the bake commands and allows applications to benefit from strict table classes even in cli.

[dereuromark]

Can we do this for 3.next? I would have to be linked somehow to application skeleton, or at least having it defined twice shouldnt matter.

[LordSimal]

Fixed via #1047
Also refs cakephp/app#1048