getEntity throwing 404 when entity is not there impact negatively observability

[albertodeago]

Is your feature request related to a problem? Please describe.
When using the getEntity method, if the entry is not there, a 404 is thrown and this impacts the observability (open telemetry), as this is seen as an error, even if I catch and swallow it because sometimes it's expected that the entry is not there in the table.
This is practically the same issue raised in the .net sdk link

Describe the solution you'd like
I'd like to have a way to get a single entity without throwing error and thus impacting my errors in my observability system.
This can be achieved by copying the solution adopted in the .net sdk link

Describe alternatives you've considered
Any alternative actually would be ok probably

• option to not throw (don't like personally)
• a method like entityExsists to just check if the entity is there
• a method getEntityIfExists that returns the entity without throwing if it doesn't find it

Additional context
nothing

[snailcatcher]

This feature would be very nice, because it allows to write the same logic in .net and js/ts

+1