SG-43999: add custom entity config features

[fauverick]

This PR introduces 4 new functions that allow users to configure custom entity (previously can only be done through the UI):

• custom_entity_read: read the config of a custom entity
• custom_entity_enable: enable & set the display name/configuration flags of a custom entity
• custom_entity_configure: configure the display name/configuration flags of an enabled custom entity
• custom_entity_disable: disable a custom entity. Will return an error if the custom entity currently has existing records. Require passing force=True to disable anyway.

Should only be merged when these methods are supported in FlowPT (once other PRs in SG-43999 are merged)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.18%. Comparing base (db056df) to head (2c2e95f).
⚠️ Report is 3 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #456      +/-   ##
==========================================
+ Coverage   78.76%   79.18%   +0.41%     
==========================================
  Files           7        7              
  Lines        1851     1869      +18     
==========================================
+ Hits         1458     1480      +22     
+ Misses        393      389       -4     

Flag	Coverage Δ
Linux	79.18% <100.00%> (+0.41%)	⬆️
Python-3.10	79.02% <100.00%> (+0.31%)	⬆️
Python-3.11	79.13% <100.00%> (+0.41%)	⬆️
Python-3.13	79.02% <100.00%> (+0.31%)	⬆️
Python-3.9	79.01% <100.00%> (+0.31%)	⬆️
Windows	79.13% <100.00%> (+0.28%)	⬆️
macOS	79.07% <100.00%> (+0.31%)	⬆️

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

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

🚀 New features to boost your workflow:

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

[fauverick]

notes: this version should be updated with the correct version once the feature is rolled out

[julien-lang]

I don't see the point having enable and disable action as API.

Basically, we want a CRUD for these custom entities. I don't know if Create and Delete are part of the scope. So basically, that should give us only 2 API methods:

• custom_entity_read
• custom_entity_update (display_name, status/enable/disable, ...)

Now, we might want to keep the custom_entity_enable and custom_entity_disable Python method as shortcuts to call custom_entity_update but then there should not be anything about display name in there.