BaseIntEnum is not handled properly in the Buildarr config parsing

[Callum027]

The following bugs occur in the current version of Buildarr:

• BaseIntEnum has no specific handlers in the default decoder and formatting functions
• When BaseIntEnum objects are exported using the JSON/YAML encoder, the BaseIntEnum encoder does not get used as BaseIntEnum is a subclass of int, so the default behaviour is used:

  jellyseerr:
    ...
    settings:
      ...
      users:
        default_permissions:
        - 1048576  # Should be 'MANAGE-ISSUES'
        - 32  # Should be 'REQUEST'

[Callum027]

It turns out this is a really tough nut to crack.

The JSON library, and literally every third-party library I've found handle built-in types as a special case, and their serialisation behaviour cannot be overridden, even by putting it in the method passed to the default parameter.

With orjson you can tell it to pass through subclasses of cardinal types such as int, and this works, but because IntEnum is a subclass of int and Enum, for some reason it does not get handled by this (it might be a bug, it might not, I don't know.)

It's looking like this might be impossible to implement, short of creating my own whole JSON library just for fixing this problem. And that's way too much work for simply being able to use integer enums wherever int values can go.

If it's not feasible to handle it properly, BaseIntEnum should be deprecated, any uses of it changed back to regular BaseEnums, and removed in the next backward-incompatible release of Buildarr (v0.5.0).