It seems that this changeset was generated because of this issue. It is a good practice to always review changesets generated by Studio before applying them on your database, especially the ones that remove tables.
Here are instructions that initially created these tables in jmix modules. You may try to create a new changeset in your app and insert these instructions there:
<createTable tableName="oauth_access_token">
<column name="authentication_id" type="varchar(255)">
<constraints primaryKey="true" nullable="false"/>
</column>
<column name="token_id" type="varchar(255)">
<constraints nullable="false"/>
</column>
<column name="token" type="${byte[].type}"/>
<column name="user_name" type="varchar(255)"/>
<column name="client_id" type="varchar(255)"/>
<column name="authentication" type="${byte[].type}"/>
<column name="refresh_token" type="varchar(255)"/>
</createTable>
<createTable tableName="oauth_refresh_token">
<column name="token_id" type="varchar(255)">
<constraints primaryKey="true" nullable="false"/>
</column>
<column name="token" type="${byte[].type}"/>
<column name="authentication" type="${byte[].type}"/>
</createTable>
<createTable tableName="persistent_logins">
<column name="series" type="varchar(64)">
<constraints primaryKey="true" nullable="false"/>
</column>
<column name="username" type="varchar(64)">
<constraints nullable="false"/>
</column>
<column name="token" type="varchar(64)">
<constraints nullable="false"/>
</column>
<column name="last_used" type="timestamp">
<constraints nullable="false"/>
</column>
</createTable>