refactor(backend): move various endpoints to modelviewsets

[matmair]

This makes it easier to have uniform URL names and behaviors; also adds a bit more testing and cleans up some path docstrings.

Still to figure out:

• bulk delete only on list endpoints
• some wired API behaviors are hard to refactor - keep them or use this to clean them up? -> added todo for now

Todo when stable:

• document how to add API endpoints the correct way

[netlify]

✅ Deploy Preview for inventree-web-pui-preview ready!

Name	Link
🔨 Latest commit	96914db
🔍 Latest deploy log	https://app.netlify.com/projects/inventree-web-pui-preview/deploys/69d9ebbba0564700098ae027
😎 Deploy Preview	https://deploy-preview-11617--inventree-web-pui-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 92 (🔴 down 1 from production) Accessibility: 81 (no change from production) Best Practices: 100 (no change from production) SEO: 78 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[codecov]

Codecov Report

❌ Patch coverage is 97.87234% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 91.35%. Comparing base (fffc55c) to head (96914db).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #11617   +/-   ##
=======================================
  Coverage   91.34%   91.35%           
=======================================
  Files         966      967    +1     
  Lines       50210    50242   +32     
=======================================
+ Hits        45866    45900   +34     
+ Misses       4344     4342    -2     

Flag	Coverage Δ
backend	89.25% <97.87%> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
Backend Apps	91.69% <ø> (ø)
Backend General	93.41% <100.00%> (+0.06%)	⬆️
Frontend	∅ <ø> (∅)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[matmair]

@SchrodingersGat would appreciate a look here. This
a) makes it harder (more explicit) to declare API endpoint that do not follow a uniform style
b) basically replaces the mixin + list + detail view ... url defintion pattern with viewset + urlregistration keeping code fragments together
c) enables us to move url definition patterns into one singe route generator instead of distributed url definitions

As seen this can be done in small steps and is still very similar to current patterns / allows reuse of current view mixins

[SchrodingersGat]

@matmair I think that this is a good move overall. Would we be looking to move a greater portion of our endpoints to this setup? Or just a small number to start with?

[matmair]

my goal would be to move all model/object based API endpoint to viewsets and keep view/function based endpoints only for stand-alone actions.

As that would be a large diff and there are small decisions to be taken regularly regarding abnormlaities in the current API I think batching this over a longer time is the way to go

[SchrodingersGat]

@matmair I'd like to get 1.3.0 out soon (as there are some major fixes that people are waiting on) - so I'll bump this to 1.4.0

[matmair]

one permission todo, then this is ready

[matmair]

@SchrodingersGat this is ready for review and merge. I have identified and documented various inconsistent API details, those are kept for now. My plan would be to do a separate PR to change these (breaking) and discuss details there then to keep this one focused on the pure refactor

[SchrodingersGat]

Nice, this is a great refactor and much cleaner code. Please address the conflict and then I'm happy to merge

[matmair]

@SchrodingersGat ready for merge