Update from 2.3.1 to 2.3.2?

This is strange, I see a prompt to 2.3.2 when I start with 2.3.1
https://drive.google.com/file/d/13cyiVsCAIl4OvYYrVRXQuMDwIQVt–AR/view?usp=sharing

When I click update, I see this:
https://drive.google.com/file/d/1SZpEZvj5ny9Btw8UUQXUYgsKHKBaHlAX/view?usp=sharing

Which then ultimately terminates in an updated 2.3.2 version:
https://drive.google.com/file/d/1rLpC7DYIvr8VEycfl7ip8QMtXS7UakAK/view?usp=sharing

I suggest to try to replace the files manually if this does not work, or eventually disabling the plugin, re-check for updates, and re-anbling helps.

Although, above screenshots are taken from an install that I tested with while crafting this reply, hence I think this should look the same on any other install as well.

Do you have any particular step or sequence that I need to follow, in order to replicate the issue?

This is surely unexpected – do you use some cache mechanisms that may keep the old issue present?
As you may know there was an issue that exactly happens as you outline, but that should be solved in the very version you mention.

However, please let me know if this works fine once you replaced the files with fresh copies (if you replace the updated version, then instead you should just see an upgrade link, and a dismissible notice about the 3.x upgrades)

This is part of 2.3.2 only thou (the notice and upgrade link)

No, that one is expected.
It’s an upgrade, not update notice, and should not worry users since it’s clear the current plugin installed is not outdated, but offers an upgrade to a paid version which can do more.