Warnings for NO_AF_LOG_ADDR are only relevant for non-mixed filters

[ankenyr]

When writing policy a mixed filter should contain the totality of terms even when some are skipped because of missing ipv4/ipv6. In the case of a ipv4 or ipv6 only filter it may be surprising to users that a filter is now no longer being output when it is expected to.

We should change logging so that NO_AF_LOG_ADDR is only emited in ipv4/6 only filters rather than mixed.

[ankenyr]

https://aerleon.slack.com/archives/C042MD2SLRX/p1689698517729279 for more context.

[XioNoX]

@jtwb Thanks! Unfortunately there is one missing case, which is

aerleon/aerleon/lib/juniper.py

Line 236 in fb514ba

self.NO_AF_LOG_PROTO.substitute(

for icmp vs. icmp6 terms.
For example I have those 2 terms in the same mixed policy file:

      - name: allow_ok_icmp4
        protocol: icmp
        icmp-type: echo-request echo-reply unreachable time-exceeded source-quench
        policer: policer-2m
        action: accept
      - name: allow_ok_icmp6
        protocol: icmpv6
        action: accept

Which outputs:

WARNING:absl:Term allow_ok_icmp6 will not be rendered, as it has icmpv6 match specified but the ACL is of inet address family.
WARNING:absl:Term allow_ok_icmp4 will not be rendered, as it has icmp match specified but the ACL is of inet6 address family.

But still creates the proper v4 and v6 terms in the relevant output file. Expected behavior is to not show those WARNING.