I am also facing the same issue. According to this page conversation I got that now contacts now migrated as acrm.schemas.contacts.read or crm.schemas.contacts.write.
But, what should I pass in scope instead of contacts in this URL if I selected both crm.schemas.contacts.read and crm.schemas.contacts.write as the scope in my app Auth tab
So the new or other scopes could be added with a space or html sign %20 to your scopes string.
But if you only select crm.schemas.contacts.read, crm.schemas.contacts.write, you cannot add automation and contacts to your Authorization URL. So you have to add the Legacy Contacts and Automation scope in you developer account. Or you have to remove them from the authorization url.
So the new or other scopes could be added with a space or html sign %20 to your scopes string.
But if you only select crm.schemas.contacts.read, crm.schemas.contacts.write, you cannot add automation and contacts to your Authorization URL. So you have to add the Legacy Contacts and Automation scope in you developer account. Or you have to remove them from the authorization url.