fix(fossid-webapp): Deduplicate and normalize ignore rules

[wkl3nk]

Deduplicate and normalize ignore rules by removing the trailing "/*" from directory rules and also remove duplicate directory,file and extension rules.
This prevents a problem where FossID reports an error when ignore rules are created that already exist.

"Scanner job '177452' failed."
java.lang.IllegalArgumentException: Could not 'create ignore rules'. Additional information: Rule already exists.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 57.30%. Comparing base (7aca3ba) to head (e4c52bf).

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #10657      +/-   ##
============================================
+ Coverage     57.25%   57.30%   +0.04%     
  Complexity     1646     1646              
============================================
  Files           341      341              
  Lines         12692    12705      +13     
  Branches       1199     1202       +3     
============================================
+ Hits           7267     7280      +13     
  Misses         4965     4965              
  Partials        460      460              

Flag	Coverage Δ
funTest-docker	71.28% <ø> (+0.04%)	⬆️
test-ubuntu-24.04	41.88% <100.00%> (+0.07%)	⬆️
test-windows-2022	41.86% <100.00%> (+0.07%)	⬆️

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

☔ 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[sschuberth]

Looks like there a space too much in between "/ *"...

[wkl3nk]

This is intentionally. If you don't add a space, then it is interpreted as the beginning of a new comment. I tried to find a solution, but adding a space is the easiest option that was returned in my searches.

[sschuberth]

Then I propose to spell it out instead, like "the trailing slash and asterisk".

[mnonnenmacher]

It's ugly, but you could close the comment with a double */*/:
https://youtrack.jetbrains.com/issue/KT-23333/Nested-multiple-line-block-comment-breaks-the-parsing#focus=Comments-27-3947881.0-0

[sschuberth]

Looks like some test needs to be adjusted.

[wkl3nk]

@sschuberth @mnonnenmacher Unfortunately the tests are still failing, as you already noticed. Please consider to merge it nevertheless, as we would like to have a new ORT release as soon as possible, as this issue currently blocks our FossID scans.

[sschuberth]

@sschuberth @mnonnenmacher Unfortunately the tests are still failing, as you already noticed. Please consider to merge it nevertheless, as we would like to have a new ORT release as soon as possible, as this issue currently blocks our FossID scans.

@wkl3nk, the test I was linking indicates there's a real (mocking) issue caused by your changes. So just rebasing does not help. You need to adjust the test.

[wkl3nk]

@sschuberth Oh sorry, yes, a test was failing and I did not recognized. I adapted the code now.