For Tridion Sites 9.0, how to apply hotfix CD_11.0.0.19562?

*** Note this KB article also applies to hotfix CD_11.1.0.19562 ***
- This article discusses possible issues which customers may encounter when applying hotfix CD_11.1.0.19562 or CD_11.0.0.19562, and/or questions administrators may have when preparing to apply the hotfix. 

Administrator notes:
- As outlined in the CD_11.0.0.19562 hotfix README (attached to this article), the hotfix involves a change to the database schema. New columns have been added to some tables, together with some updated indexes and constraints. 
- If necessary to rollback, stop services, restore original database(s), restore original services, and restart services.
- All existing CD microservices need to be updated.
- Future CD hotfixes will require this hotfix (or the 9.1 surrogate key hotfix counterpart) to be installed first.
- If the state store database is outscaled and is separate from the broker database, the hotfix database script does not need to be run against the state store database.
- Non-alphanumeric characters in the broker database user password may cause the hotfix Upgrade Content Data Store.ps1 script, to fail as discussed in below KB article.  To address this, temporarily change the password to run script and restore original password after successfully running script.
For Tridion Sites 9.0, applying hotfix CD_11.0.0.19562 fails with error "Unexpected error running Liquibase: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user"
- One customer needed to apply a custom index to the CUSTOM_META table after applying hotfix as discussed in KB article, but this likely is not related to the hotfix itself.
For Tridion Sites 9.0, deadlock victim publishing error after applying CD hotfix CD_11.0.0.19562
- Customers may see that publishing fails as discussed in KB article below.
For Tridion Sites 9.1, error "SqlExceptionHelper - Duplicate entry ... for key 'PRIMARY'" when attempting to publish a category
- Customers may see that database upgrade fails as discussed in KB article below
For Tridion Sites 9.1, Powershell error "Method invocation failed because [System.Net.NetworkCredential] does not contain a method named 'new'." when applying hotfix CD_11.1.0.19562
- Customers using DXA may see that pages fail to display with 500 error as discussed in KB article
For Tridion Sites 9.1, DXA pages fail to display with error "PCA client returned an unexpected response when retrieving page model data for page url" after applying hotfix CD_11.0.0.19562

For Tridion Sites 9.0, hotfix CD_11.0.0.19562 is also included in the Sites 9.0 CU1 update.  So alternatively, the hotfix can be applied via the update.
https://docs.sdl.com/792149/833906/sdl-tridion-sites-9/content-delivery-hotfixes
Note that if either surrogate key hotfix is already installed (CD_11.0.0.19562 or CD_11.1.0.19562), and an administrator attempts to apply CU1 for Tridion Sites 9.0, the CU1 upgrade script for the broker database will fail as the Liquibase ID can't be overwritten once a surrogate keyhotfix is installed.  Also upgrading from 9.0/9.1 to 9.5 will also fail.

See KB article SDL Tridion Sites 9.x - Database upgrade returns error on liquibase ID for steps to address this.