feat: query get_operation_records prints correct errors

[SteBaum]

Which issue(s) this PR fixes

Fixes #483

Additional comments

Modified the error handling to print the right messages

Agreements

• I hereby declare this contribution to be licensed under the Apache License Version 2.0, January 2004.
• I hereby agree to grant TOSIT a copyright license to use my contributions.

[PaulFarault]

This PR defines 2 queries in one. It makes code way more complicated and does not provide much value.

Checking if the deployment exist may be a good idea but it should be done in it's own query.

[PaulFarault]

Focus on resolving the issue mentioned by @sergkudinov on this PR:

When you changed to .all() here, the NoResultFound exception is never raised.

Then, we could study how to raise a more specific Error.

As now we're doing 3 queries which seems a lot.

[SteBaum]

Opted for a very simple change, to through an error if no results are found and modified the message to incorporate the two possibilities.

[PaulFarault]

You can even be more generic:

Suggested change

	f"Operation {operation_name} does not exist in deployment {deployment_id} or deployment {deployment_id} does not exist."
	)
	f"Can't find operation {operation_name} for deployment {deployment_id}."
	) from e

[SteBaum]

The whole point of the prolonged message was to state the two possible issues with the query, either the operation does not exist in the chosen deployment or the deployment itself does not exist. this message is more specific.
However I can change above the raise Exception to raise NoResultsFound which is also more specific.