Create the extra_property_definition_shop table in the 9.2.0 upgrade script

[jolelievre]

Description

Companion to two core PRs touching the extra property registry schema for 9.2.0:

• Allow restricting extra property definitions to a list of shops PrestaShop#42490 (merged) — lets an extra property definition be restricted to a list of shops through a new extra_property_definition_shop association table (created at install in install-dev/data/db_structure.sql).
• Handle non-conventional entity naming, default value typing and the cart entity in extra properties PrestaShop#42538 — supports entities with non-conventional naming (Order → orders, Combination → product_attribute) by persisting the resolved physical table in a new nullable table_name column on the extra_property_definition registry.

This PR adds the matching DDL to upgrade/sql/9.2.0.sql: the extra_property_definition_shop CREATE TABLE IF NOT EXISTS right below the extra_property_definition registry table it references, and the table_name column in that registry table's definition — both with the same column definitions and keys as the install structure.

No data seeding is needed: the absence of association rows is the shop feature's backward-compatible default ("no explicit restriction"), and a NULL table_name falls back to the entity name, which is correct for every definition created before #42538 (conventional naming was the only possibility).

How to test

• Upgrade a 9.1.x shop to a 9.2.0 build containing both core PRs (or execute the new statements against a 9.2.0 database): SHOW CREATE TABLE ps_extra_property_definition_shop returns the table with the composite (id_extra_property_definition, id_shop) primary key and the id_shop key, and SHOW COLUMNS FROM ps_extra_property_definition LIKE 'table_name' returns the nullable varchar(64) column — identical to a fresh install.
• Running the script twice raises no error (CREATE TABLE IF NOT EXISTS).
• On the upgraded shop with multistore enabled, Advanced Parameters > Extra Properties renders and saving a store association on a definition persists rows in the new table; registering a definition on the combination entity stores table_name = product_attribute.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud