[client] Remove setuptools from project requirements

[fslds]

Setuptools is defined in the project requirement, but it seems that no code (as it should) relies on setuptools and this is merely a build requirement. As such I have removed it from requirements.txt and setup.cfg.
This change should increase overall compatibility and reduce version conflicts (as I have experienced), without impacting functionality.

Proposed changes

• Remove setuptools from project requirements.

Related issues

• n/a

Checklist

• I consider the submitted work as finished
• I tested the code for its functionality
• I wrote test cases for the relevant uses case
• I added/update the relevant documentation (either on github or on notion)
• Where necessary I refactored code to improve the overall quality

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

[helene-nguyen]

@fslds Thank you for your contribution !

We work aside to use another tool for package management, for now setuptools here is required in our usages and cannot be removed. I close the PR for now, and I've created an issue to follow the updates: OpenCTI-Platform/opencti#13375

[fslds]

Ahh that's nice! But I just want to add the problem is not the packaging itself, it is that it ends up being a package dependency, which it shouldn't.

You just make sure setuptools (or whichever build tool) is present when building, worst case a separate requirement group, but not as a part of the main dependencies.

[helene-nguyen]

@fslds Thank you, we will work on it !