Support deduplication of modules where an output is being used as a source in BoringUtils.bore()

@jackkoenig @seldridge

**Type of issue**: Feature Request

**Is your feature request related to a problem? Please describe.**

Sometimes it is useful to using BoringUtils.bore() with the source being an output of a deduplicated macro

**Describe the solution you'd like**

Deduplication should work.

**Describe alternatives you've considered**

Connecting to a wire in the module that instantiates the module that I want to bore to.

**Additional context**

Deduplication not working for Element:

https://scastie.scala-lang.org/9ILfIwIvQZa8EiIvL0lQzg

**What is the use case for implementing this feature?**

Start by reproducing the linked Scastie example and reading BoringUtils.bore() behavior around outputs from deduplicated macros. Trace the deduplication handling for Element outputs and locate related tests. Done means BoringUtils.bore() supports a source that is an output of a deduplicated macro, with regression coverage.

Written by the indexing model from the issue text.