Add support for similar waste types with different API IDs

[EyeDevelop]

Proposed Changes

This PR adds a fall-through method to the WasteType enum. The Twente Milieu API might return a waste type that is almost the same as one already defined in the enum.

Hengelo now has pick-up points for packaging and paper for high-density living. For the packaging, they created a new waste type. However, it is still packaging. This change now maps the 'odd' waste type returned from the API to the packages value in the enum.

Please let me know what you think!

Related Issues

#1265

[frenck]

Hi there @EyeDevelop 👋

CI is failing, could you please take a look?

../Frenck

[EyeDevelop]

Hi @frenck, I (should) have resolved all the issues with CI. Can you take a look?

I like the idea of having strict coding guidelines enforced with these typing rules and test coverage. However, if I could make a suggestion it would be to loosen them in some cases. For the _missing function I added to the IntEnum, mypy made a note that value should be of type object. However, in practice this can never be anything other than int unless the _missing_ function is directly called. You can see in the test I added that I have to call the method directly to comply with the 100% coverage. It is my opinion that these are not really useful additions, but I leave this up to you.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (7c783e6) to head (95481e9).
Report is 362 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #1267   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines           95       100    +5     
  Branches        15        12    -3     
=========================================
+ Hits            95       100    +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[frenck]

However, if I could make a suggestion it would be to loosen them in some cases.

Sorry... I strongly disagree very much. Don't know what else to say.

Left a few review comments and the CI is also failing (which is odd? As ruff is run in pre-commit... not sure how you manage to make a commit that passes it).

../Frenck

[EyeDevelop]

Processed your review comments. Let me know if I should drop the first commit with the changes to the dev container file.

[frenck]

Thanks, @EyeDevelop 👍

../Frenck