Added exception when replanner remove_{action/goal} fails

[Framba-Luca]

Now the integrated meta-engine replanner does not silently fail when a remove_action or remove_goal does not change the problem.

[Framba-Luca]

Thinking about this feature, we could insert a flag that determines if the user wants an exception when the method fails (default behavior) or he prefers a silent fail.

Issues I currently see:

• with the flag: maybe not every replanner can support both behaviors, so we would be adding a flag in the replanner interface that might not work for some replanners (clashes with the idea 100% interchangeable engines)
• without the flag: the default behavior is an exception, but if a replanner silently fails, we get the same issue of above

[codecov-commenter]

Codecov Report

Patch coverage: 91.30% and project coverage change: +0.01% 🎉

Comparison is base (6d3cbec) 85.03% compared to head (d4c1db0) 85.04%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #474      +/-   ##
==========================================
+ Coverage   85.03%   85.04%   +0.01%     
==========================================
  Files         198      198              
  Lines       26019    26042      +23     
==========================================
+ Hits        22125    22148      +23     
  Misses       3894     3894              

Files Changed	Coverage Δ
unified_planning/engines/mixins/replanner.py	84.90% <ø> (ø)
unified_planning/engines/replanner.py	96.00% <87.50%> (+1.08%)	⬆️
unified_planning/test/test_replanner.py	100.00% <100.00%> (ø)

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