fix: Only take a new attempt on beginAttempt for items which endAttempt was invoked to allow skipped items to be navigated freely

[quintanilhar]

Ticket

https://oat-sa.atlassian.net/browse/TR-1241

Summary

A test taker can decide to skip an item for non-linear tests with items configured with multiple attempts, however, it should not take an attempt away, it should rather put the item in suspend mode and resume the attempt once the item is displayed again. This is done currently by the action endCandidateSession. This is a valid operation but it's currently calling the endAttempt method underneath.

This PR introduces 2 changes to avoid taking attempts away incorrectly:

1- Remove the endAttempt call from the endCandidationSession method;
2- Add a new condition before considering a new attempt to check if the attempt was really ended by the test taker (with endAttempt call);

Dependencies

No dependencies

[julien-sebire]

Good job. It seems all good for me.
Thanks for updating the tests.

[poyuki]

• New code is covered by tests (if applicable)
• Tests are running successfully (old and new ones) on my local machine (if applicable)
• New code is respecting code style rules
• New code is respecting best practices
• New code is not subject to concurrency issues (if applicable)
• Feature is working correctly on my local machine (if applicable)
• Acceptance criteria are respected
• Pull request title and description are meaningful
• Pull request's target is not master
• Commits are following conventional commits
• Changelog is updated according to changes (if applicable)
• Documentation is updated according to changes (if applicable)