Description

Previously, we only checked if the variable to be range checked externally was at L xor R locations in the gate. In this PR we remove the restrictions that we can use a gate only a single variable range check. Additionally, we also output now if the variable is in the O location in the gate.

Type of change

• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How has this been tested?

In downstream usage

Checklist:

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• I did not modify files generated from templates
• golangci-lint does not output errors locally
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules