Implement argument dealiasing

[asl]

After p4lang/p4c#5318 we might be in perfect position to simplify / optimize copy-in / copy-out semantics before inlining. This would eliminate variables for copy-in / copy-out values

Essentially we can check if the extern / action / function call arguments alias each other. E.g. for the following code:

      p4hir.scope {
        %int_egress_port_tx_utilization_header_field_ref = p4hir.struct_extract_ref %arg1["int_egress_port_tx_utilization_header"] : <!headers>
        %hdr_out_arg = p4hir.variable ["hdr_out_arg"] : <!int_egress_port_tx_utilization_header_t>
        p4hir.call_method @packet_in::@extract<[!int_egress_port_tx_utilization_header_t]> of %arg0 : !packet_in (%hdr_out_arg) : (!p4hir.ref<!int_egress_port_tx_utilization_header_t>) -> ()
        %val = p4hir.read %hdr_out_arg : <!int_egress_port_tx_utilization_header_t>
        p4hir.assign %val, %int_egress_port_tx_utilization_header_field_ref : <!int_egress_port_tx_utilization_header_t>
      }

We can eliminate hdr_out_arg and pass reference to a header field directly. For this we need:

• Identify set of variables used to hold inout / out arguments along with corresponding source / destination arguments
• Ensure that source / destination arguments do not alias each other (to exclude e.g. foo(s, s.field) cases)
• Ensure that copy-in / copy-out variables has one (for inouts) or zero (for outs) write before call and exactly one read after the call
• And Check for out/inout bindings aliased with uses p4c#5318 ensures that there are no "side" channels (though after Make actions / functions / controls isolated #195 we can do same kind of check pretty trivial as well – yay to isolation, all external uses are explicit!)

[asl]

Things to consider:

1. Direct function calls
2. Calling top-level actions (should be similar to direct function calls as these does not access "global" scope)
3. Subparser / control apply
4. Extern calls
5. Extern method calls
6. Actions inside controls

Without p4lang/p4c#5318 we need to check if callee would have access to aliased arguments. After it we can just reason on potential side effects based solely on the inout / out annotation. We'd still need to do proper alias analysis though

[asl]

Mostly done in #249. Need some AA to better model copy-in / copy-out semantics (currently we're conservative wrt projections / field references)