[FIRRTL] Don't Dedup Modules with Different NestedPrefixModulesAnnotation

NestedPrefixModulesAnnotation with different prefixes should not deduplicate. This can be interpreted one of two ways, either of which should have the same effect:

1. NestedPrefixModulesAnnotation should block deduplication.
2. The PrefixModules pass should duplicate modules which have different prefixes.

SiFive's extensions to the SFC are implementing this using strategy (2).

An end-to-end test case that should work is the following:

circuit Foo: %[[
  {
    "class":"sifive.enterprise.firrtl.NestedPrefixModulesAnnotation",
    "prefix":"prefix1_",
    "inclusive":true,
    "target":"~Foo|Bar"
  },
  {
    "class":"sifive.enterprise.firrtl.NestedPrefixModulesAnnotation",
    "prefix":"prefix2_",
    "inclusive":true,
    "target":"~Foo|Baz"
  }
]]
  module Bar:
  module Baz:
  module Foo:
    inst bar of Bar
    inst baz of Baz

Currently, this produces (firtool -dedup -strip-debug-info):

module prefix2_Bar();
endmodule

module Foo();
  prefix2_Bar bar ();
  prefix2_Bar baz ();
endmodule

This should produce:

module prefix1_Bar();
endmodule

module prefix2_Baz();
endmodule

module Foo();
  prefix1_Bar bar ();
  prefix2_Baz baz ();
endmodule

There may also be an interaction here with memories where memories should not deduplicate if they have different prefixes. This may be a little funky because it has interactions with the memory generator schema which may not respect prefixing.

Start by reproducing the provided FIRRTL circuit with firtool -dedup -strip-debug-info, then read the PrefixModules pass and the deduplication path it interacts with. Check the possible memory-generator interaction described in the issue. Done means the example preserves prefix1_Bar and prefix2_Baz as separate modules with the corresponding instances, with coverage for the differing prefixes.