Update older `appearance`migration in EE because it conflicts when upgrading from CE
We recently backported the appearance feature from EE to CE. The migration in CE used a conditional check to make sure the table didn't already exist. We should add that same conditional check to the older EE migration so users upgrading from CE to EE don't get the following error:
PG::DuplicateTable: ERROR: relation "appearances" already exists