file conflict when installing libsgutils-2-1.46-2 when upgrading from lunar to mantic

I was able to remove the old package and continue the installation this way:

```
dpkg -r libsgutils2-2
apt-get --fix-broken install
apt-get dist-upgrade
```

This is another case that if the upgrade is done with do-release-upgrade(8), the file conflict is overridden and not noticeable:

Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2) ...
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1

Just to confirm, Thomas, did you use "apt-get dist-upgrade" for this upgrade from lunar to mantic?

I think this has been caused by https://salsa.debian.org/linux-blocks-team/sg3-utils/-/commit/0d53f3311b6657040b23f851a47c429c49cae0e9. It should be a matter of adjusting Conflicts/Replaces accordingly for Ubuntu.

These are the affected ubuntu releases with conflicting files:

Jammy: 1.46-1build1
package: libsgutils2-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0

Lunar: 1.46-1ubuntu0.23.04.1
package: libsgutils2-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0

Mantic: 1.46-3ubuntu2
package: libsgutils2-1.46-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0

Upgrades from jammy to mantic will also see this bug, when lunar goes EOL.

This seems to be one of the unsolved cases in the debian package transitioning guide[1]. We need a breaks/replaces for all versions in jammy and lunar, including updates that are yet to become available. In summary, anything 1.46-1*.

If we do:
Breaks: libsgutils2-2 (<< 1.46-3ubuntu2)
Replaces: libsgutils2-2 (<< 1.46-3ubuntu2)

This will include versions like focal's 1.44-1ubuntu2, which isn't affected (the library file there was still called libsgutils2.so.2, so no file conflict). That being said, we don't expect someone from focal to upgrade to mantic without going through jammy first, at least. And once in jammy, the version in B/R from mantic is correctly targeting the jammy version.

I'll give this a try and run some tests.

1. https://wiki.debian.org/PackageTransition