Enable manifest v2 after June 2025

[Nghia323223]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
As you already know, in June 2025 Chrome/Chromium will lose the ability to use Manifest V2. This is not going to be good if users do not move to firefox-based browsers yet.
Describe the solution you'd like
A clear and concise description of what you want to happen.
I want to know what type of source code will you add to supermium, so that even after Manifest V2 being removed by Google (to sustain fixers' trust, of course), so that I can help Ungoogled-Chromium stay at Manifest V2, ultimately helping all Chromium users.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
For now, I have found out a way for force it is to add the given Manifest V2 extension to the forced install list, but that might not work anywhere.
Additional context
Add any other context or screenshots about the feature request here.
I have looked a lot into the source code, yet haven't found the solution yet. I need a way to get deeper into this problem, be it source code or flags (if you haven't write the source yet) to help the Ungoogled-Chromium community.

[EDSln]

That's what it says in the description:

Future support for:
-Manifest V2 (once removed by Google)

[win32ss]

MV2 support code will be retained by reverting the commits that remove it, when Supermium is actually affected by the code removal, which will be when we are forced to go to 138 ESR tags in July or August. I suspect it will be a fairly complicated process and require frequent refactors per ESR (so once every 6 versions/every 6 months) but I am committed to it, because many MV2 extensions are too useful to be dropped, especially content blockers that allow users to remove any objectionable element on a webpage, which MV3 extensions seemingly cannot do.

MV2 support will likely be controlled by a flag (but enabled by default). MV3 extension signing will follow the same path if necessary.

[EgorKuzevanov]

MV2 support code will be retained by reverting the commits that remove it, when Supermium is actually affected by the code removal, which will be when we are forced to go to 138 ESR tags in July or August. I suspect it will be a fairly complicated process and require frequent refactors per ESR (so once every 6 versions/every 6 months) but I am committed to it, because many MV2 extensions are too useful to be dropped, especially content blockers that allow users to remove any objectionable element on a webpage, which MV3 extensions seemingly cannot do.

MV2 support will likely be controlled by a flag (but enabled by default). MV3 extension signing will follow the same path if necessary.

win32ss, in addition to ad blockers such as uBlock Origin, there are other Chromium extensions that have not yet migrated from Manifest v2 to Manifest v3. One of them is the SimpleExtManager extension (https://chromewebstore.google.com/detail/simpleextmanager/kniehgiejgnnpgojkdhhjbgbllnfkfdk and https://www.crx4chrome.com/extensions/kniehgiejgnnpgojkdhhjbgbllnfkfdk), which I use for quickly enable/disable extensions for bypass Internet censorship in Russia (Browsec VPN, Censor Tracker, official RuTracker extension, etc.) in 2-3 mouse clicks, because only one of these extensions can control proxy server settings in Supermium.

[Half-Modern]

That's what it says in the description:

Future support for: -Manifest V2 (once removed by Google)

He doesn't read the description, that's why this has been opened. But he mustn't be reading the replies either, hence it's still open.