Thanks, #34 worked for me as well.
I think this patch may have unintended consequences. Today I upgraded from D9 to D10. When I attempted to run database updates, I was stuck on this patch. I do not have a table file_managed_data, only files_managed. I was able to move past this by duplicating files_managed as files_managed_data. After the migration, I tested my content, and no files/data are being inserted into file_managed_data, so I just removed the unnecessary file_managed_data table.
Thanks for the update on this. I was just coming back to look into this with other contrib module updates and saw the fix. I added as a packaged repository in composer, and it seems to work as expected.
I ran into this same problem, and it seemed at first if the patch in #31 worked. However, when I looked a little more closely, I realized the actual issue was that my custom theme was calling two libraries that were not actually enabled (one via a module, one via a theme). These calls were outdated, so once I removed, the notice disappeared, even without this patch.
Thanks for this - #11 also worked for me using a custom conf file with Lando.
Just a followup for #15 – you will want to include ^2.0 || ^3.0 directly in your composer file. Running the listed command will just require 2.0, since composer sees the pipes as a new command.
Patch #30 works for me, thank you!
Just in case anyone is still seeing this, I noticed the same error message in my logs recently. Apparently in my case, the issue is that I have a single Webform submission that creates multiple SF records. On return, only one SF record can be mapped to the Webform submission. The error doesn't seem to have any effect on the actual SF records creation.
The reason why it works for @ahmadhalah is because of the values used for "module" and "key." Those reference the test email send through the SMTP configuration. So the errors that the OP is seeing are due to that, and due to the SMTP module not being referenced properly in the mail service.