API rescue master-branch PR: Shorten auto-generated table names #7621

[GuySartorelli]

Rescues PR #7621 from the master branch.

Note that I have also added a commit on top of it which un-deprecates the warning for DataObject classes which are missing a table_name (added in #7620 as a companion to #7621) as I believe it promotes best practices and still protects against table names that may still be too long.

Parent issue

• Rescue master branch commits #10350

[GuySartorelli]

@emteknetnz You haven't asked me to change anything for this PR but also haven't merged it - I don't want to read into potential implications so can you please specify whether you want some changes made to this PR, and if so, what those changes are?

[emteknetnz]

This has caused a regression

1) SilverStripe\i18n\Tests\i18nTest::testGetExistingTranslations LogicException: Multiple classes ("SilverStripe\AssetAdmin\Tests\GraphQL\UnpublishFileMutationCreatorTest\FileOwner", "SilverStripe\AssetAdmin\Tests\Forms\FileFormBuilderTest\FileOwner") map to the same table: "SilverStripe_FileOwner" in /var/www/vendor/silverstripe/framework/src/ORM/DataObjectSchema.php:299

I tried reverting the change on my local and the issue went away

[GuySartorelli]

@emteknetnz We could set explicit table_name config for each of those classes, but honestly this change that caused the regression is probably going to cause more pain than it's worth. I'm in favour of just reverting it. Do you agree?