Make error messages consistent and uniform across python and go SDK

[shramroy]

Observation from Snappi version: 0.6.5

Some error message I am mentioning here for example -

1. '0 <= PatternFlowIpv4TosReliability.Value <= 1 but Got 2\nvalidation errors'

• suggested way - PatternFlowIpv4TosReliability.Value is not in range [0, 1]

2. 'PortName is required field on interface DeviceEthernet'

• Adding line number for which error is coming will be helpful for this type of scenarios.

[ashutshkumr]

@ajbalogh FYI

We need to put some effort in ensuring that error is more consistent. Some basic rules that we need to follow are:

• Use node names as used in openapi yaml. e.g. ipv4.src.value instead of PatternFlowIpv4Src.Value
• Try to pinpoint exact node in which error occurred. e.g. flows[0].packet[1].src.value
  • This maybe a little difficult to achieve, but failing to provide exact node where the error occurred might be confusing

Before implementing this, let's have a list of all possible errors for an example node and see if they look ok.