[BUG REPORT] Snapcraft version of brave browser use a bad folder to save user data

Description of the issue:
The snapcraft version of brave saves the user data in a folder that is revision dependent. So when the browser auto-updates when running in the same time, all data save after the update is saved in an old folder, thus giving the illusion that all the data is lost after the update.

Steps to Reproduce:
Note the revision folder name in /home/username/snap/brave. Then launch Brave.
2. Wait for an update to be made. The revision folder number will be incremented.
3. Generate user data (create bookmarks for exemple)
4. You can see that the data is saved in the first revision folder instead of the last (or better: the folder “common”)

Expected Result:
User data is saved in a non revision dependent folder

Reproduces how often:
Each new update

Brave Version:
Version 1.38.119 Chromium: 101.0.4951.67 (Official Build) (64-bit)

Snapcraft version : 161

Reproducible on current live release :

Additional information:
I’m using Linux.
Probably just a constant is to change in the snapcraft package, here is the doc page :

An additional post from the snapcraft forum : https://forum.snapcraft.io/t/disable-auto-refresh-or-hotswaping-config-folders/30070

The interesting quote from the link above:
As described in https://snapcraft.io/docs/data-locations snaps have SNAP_USER_COMMON which is a fixed path for all revisions of the app and is’a fixed path at $HOME/snap/<name>/common. The brave snap should be using this instead of $SNAP_USER_DATA.