feat: Logo detection

[smereu]

Description

Exposes logo detection and removal. Logos is exposed as a problem area defined by a list of faces. There is no ability to distinguish multiple logos if present so we expose a single problem area. The problem area has a fix method to remove the logo. There is a find and remove method that allows to remove everything automatically.

Issue linked

Checklist

• I have tested my changes locally.
• I have added necessary documentation or updated existing documentation.
• I have followed the coding style guidelines of this project.
• I have added appropriate unit tests.
• I have reviewed my changes before submitting this pull request.
• I have linked the issue or issues that are solved to the PR if any.
• I have assigned this PR to myself.
• I have added the minimum version decorator to any new backend method implemented.
• I have made sure that the title of my PR follows Conventional commits style (e.g. feat: extrude circle to cylinder)

[smereu]

@RobPasMue My previous branch for logo detection had too many conflicts and I was getting a hard time with it so I created a new one and a new pull request. There is a small fix pending on the API server then it will be ready for full review

[RobPasMue]

@RobPasMue My previous branch for logo detection had too many conflicts and I was getting a hard time with it so I created a new one and a new pull request. There is a small fix pending on the API server then it will be ready for full review

Hi @smereu - does that mean we can close #1819?

[smereu]

@RobPasMue I added some check for disabling on Linux but I am not sure if it is the correct way to do it. Should I log an issue for it? Also there is one change in the API server that has to be merged otherwise one of the asserts will fail.

[RobPasMue]

@RobPasMue I added some check for disabling on Linux but I am not sure if it is the correct way to do it. Should I log an issue for it? Also there is one change in the API server that has to be merged otherwise one of the asserts will fail.

Hi @smereu -- I can't see any "skip on Linux" condition on your PR, sadly. That's what's causing the CI/CD to fail I guess.

[RobPasMue]

Requesting a few changes -- nonetheless, the PR is looking good, thanks @smereu!

[smereu]

@RobPasMue I hope I addressed the comments. I will add the quantity input to this method together with all the other ones.
The failing test needs a new build of API server. I could address it now but it will start failing with a new build

[RobPasMue]

Hi @smereu - changes look good. Thanks for addressing them. I think there are only 2 comments missing to be resolved:

1- I'd rather access by name (inside the test) whenever we want to validate number of faces of a given body. I'd search for the component with the desired name - and for the specific body we want (also by name), and then validate its face number.
2- I don't think we need the modeler inside prepare tools based on the operations you are performing (just retrieving the backend type). That information is available inside the client already so there is no need for the modeler =)

[codecov]

Codecov Report

Attention: Patch coverage is 90.19608% with 5 lines in your changes missing coverage. Please review.

Project coverage is 90.18%. Comparing base (c202b02) to head (feb9603).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
src/ansys/geometry/core/tools/prepare_tools.py	84.84%	5 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1873      +/-   ##
==========================================
- Coverage   90.18%   90.18%   -0.01%     
==========================================
  Files          92       92              
  Lines        8852     8902      +50     
==========================================
+ Hits         7983     8028      +45     
- Misses        869      874       +5     

☔ View full report in Codecov by Sentry.
📢 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.

[RobPasMue]

Implementation looks good @smereu - thanks for handling all my comments!