Support Non-Standard Command Syntax in Network Intent Execution

Network Intent and parser-based execution currently cannot process CLI commands where the primary command keyword appears at the end of the command string rather than as a leading prefix, even though such commands execute successfully through standard CLI Commands. This limits the ability to use Network Intent for device command sets that follow non-standard syntax conventions. This enhancement would extend Network Intent and parser command matching logic to recognize and execute commands regardless of keyword position within the command string. Supporting flexible command formats would allow customers with non-standard CLI syntax to fully leverage Network Intent automation and parsing capabilities without needing to restructure existing command sets.