chore: Align Aviator exception handling with Aviator simple/technical exceptions

[kireetivar]

Summary

• replace raw RuntimeException and IllegalStateException wrappers at Aviator technical-failure boundaries with AviatorTechnicalException
• use AviatorSimpleException for direct user/config validation failures in Priority and NumberRangeComparer
• add focused regression coverage for the changed technical-exception boundaries
• update the existing NumberRangeComparer test to expect AviatorSimpleException

Details

This change keeps Aviator exception handling aligned with fcli conventions:

• technical failures remain technical:
  • FPR metadata parsing
  • filtertemplate.xml parse/save failures
  • hashing helper failures
  • gRPC message-to-JSON conversion failures
  • direct invalid input/config validation is surfaced as simple:
  • invalid priority values
  • malformed numeric range syntax