docs: rai simbench docs update

[jmatejcz]

Purpose

Fixing couple small issues that were occuring during execution:

• Some scenarios didn't have proper level assigned
• Errors were catched in a manner that was not informative and lead to further execution
• Fixed response returned by MoveObjectFromToTool

Proposed Changes

• Now all scenarios have proper level assignment in predefined scenarios
• Errors are now catched in test_models function instead of in run_next. Before that when an unexpected exception occured, it would affect the single scenario execution. After that the next scenario would execute as planned, but that was the problem, because usually the problem was outside of scenario scope and would reoccur in every scenario till the end - for example cuda OOM. In such case it was a wasted time and the avg scores were impared by the 0.0 scores that were result of error.
  Now when unexpected error occurs the whole benchmark will stop, preserving the scores that were achieved till this moment.

Issues

Testing

Just run manipulation benchmark

python src/rai_bench/rai_bench/examples/benchmarking_models.py

you can check out the logs to see that levels are assigned properly

[Juliaj]

@jmatejcz , could this PR use a rebase ?

[jmatejcz]

@jmatejcz , could this PR use a rebase ?

it is fine now, but i removed poetry lock which was accidentally added add looked like a lot of lines changed