address_update_9201() can fail if row format is not set to dynamic

We had the same issue.
Our database version was updated from mariadb:10.0 to mariadb:10.3.
row_format of tables was changed:

ALTER TABLE commerce_store_field_data ROW_FORMAT=DYNAMIC;
ALTER TABLE profile__address ROW_FORMAT=DYNAMIC;
ALTER TABLE profile_revision__address ROW_FORMAT=DYNAMIC;

And columns were dropped before running update.

ALTER TABLE commerce_store_field_data DROP COLUMN address__address_line3;
ALTER TABLE profile__address DROP COLUMN address_address_line3;
ALTER TABLE profile_revision__address DROP COLUMN address_address_line3;

+1 to the resolution by @andriic.

I will add that there was a table in the db I was working on that required more work. For this table, I had to manually resize some columns from the default `varchar(255)`.

I used this command to return a integer for each row found in a column that exceeded a specific limit:
`SELECT COUNT(*) AS count_exceeding_XX FROM your_table WHERE LENGTH(your_column) > 50;`
Note: `count_exceeding_XX` is an arbitrary value. It can be named anything.

Then once I noted the lowest reasonable size I could set a column, I set it to the desired value by:
`ALTER TABLE your_table MODIFY COLUMN your_column VARCHAR(50);`