HTTPSE upgrades not working with Chromium 101

Description

HTTPSE upgrades are not working with 1.38.x w/ Chromium 101. They do work on 1.37.x with Chromium 100.

When using 1.38.x, doesn’t matter if shields v2 are enabled or not.

Worked with 1.38.103 which had Chromium 100, does not work with Chromium 101 versions of 1.38.x.

Steps to Reproduce

1. Clean profile 1.38.105
2. Navigate to http://https-everywhere.badssl.com/

In general, we should ensure that HTTPS redirects are working as expected on new/older profiles. As per @mkarolin, we should also ensure that HTTPS redirects are working with profiles that have the following directory already created:

<PROFILE_DIR>/oofiananboodjbbmdelgdommihjbkfag/1.0.91/6.0/httpse.leveldb

Actual result:

not upgraded to https with 1.38.x with either shields v1 or v2

v1	v2

Expected result:

upgraded to https as in 1.37.x

Reproduces how often:

easily

Brave version (brave://version info)

Brave	1.38.105 Chromium: 101.0.4951.41 (Official Build) (x86_64)
Revision	93c720db8323b3ec10d056025ab95c23a31997c9-refs/branch-heads/4951@{#904}
OS	macOS Version 12.3.1 (Build 21E258)

Version/Channel Information:

• Can you reproduce this issue with the current release? 1.37.x no, 1.38.x yes
• Can you reproduce this issue with the beta channel? probably
• Can you reproduce this issue with the nightly channel? 1.40.x yes

Other Additional Information:

• Does the issue resolve itself when disabling Brave Shields?
• Does the issue resolve itself when disabling Brave Rewards?
• Is the issue reproducible on the latest version of Chrome?

Miscellaneous Information:

cc @rebron @mkarolin

[GeetaSarvadnya]

Verification PASSED on

Brave | 1.38.107 Chromium: 101.0.4951.41 (Official Build) (64-bit)
-- | --
Revision | 93c720db8323b3ec10d056025ab95c23a31997c9-refs/branch-heads/4951@{#904}
OS | Windows 10 Version 21H2 (Build 19044.1645)

Clean profile

• Confirmed that HTTPS upgrade works fine in 1.38.107 in a clean profile

Upgrade profile

• Confirmed that HTTPS upgrade works fine in an upgraded profile

• Confirmed that HTTPS upgrade works in a profile where ...User Data\oofiananboodjbbmdelgdommihjbkfag\1.0.91\6.0\httpse.leveldb is already created

Example	Example

[kjozwiak]

The above will require 1.38.107 or higher for 1.38.x verification 👍