Represent features using primitive types and `IntEnum`/`StrEnum` instead of immutable `Enum`s for extensibility

What is the use case for the feature?

Adding new feature support to ofrak and ofrak_patch_maker should not require forking this repository to modify internal types or hacking together fake Enum member objects. We should use bare Enum when it's suitably internal and not intended to be extensible or it's possible to actually enumerate all possible options (endianness, memory permissions, etc. probably qualify here).

Example of Enums that shouldn't be

• ElfSectionType
• ElfProgramHeaderType
• Every Enum in ofrak_type.architecture

Does the feature contain any proprietary information about another company's intellectual property?

No.

How would you implement this feature?

Changing "feature" Enums to inherit from StrEnum or IntEnum and update typedefs in consuming classes/methods to str or int.

Are you interested in implementing it yourself?

Yes.

Start by inventorying Enum definitions in ElfSectionType, ElfProgramHeaderType, and ofrak_type.architecture, then trace their consuming classes and methods. Determine which types need primitive-compatible extensibility and update the affected typedefs consistently. Done means new OFRAK and ofrak_patch_maker feature values can be added without modifying this repository or creating fake Enum members.