Furo looks bad with methods on same page as class

[Eric-Arellano]

See

The specific problem is when you highlight over the header for the method, a # anchor pops up. That overlaps with the [source] button. This is why we have this rule in our CSS atm:

qiskit_sphinx_theme/src/qiskit_sphinx_theme/assets/styles/_api.scss

Lines 17 to 37 in 10fff40

	// Rules that impact the top-level entry for the code object, which e.g. has the `[source]` button.
	section > dl.py:not(.docutils) {
	> dt {
	// We normally want to use inline-block for definition terms so that the purple border we add on
	// top does not stretch across the whole screen. But, we make an exception here it will have a
	// `[source]` button that floats to the right. The spacing of that is non-trivial and was the
	// source of issues in Pytorch, so we stick with Furo's spacing.
	display: block;
	// Make the border less thick so its clear the top-level page header corresponds to this line.
	border-top-width: 1px;
	margin-bottom: 1rem;
	}
	// It's possible to have multiple entries for the same code object, e.g. when using typing.overload.
	// This cancels out the margin-bottom such that only the bottom-most `dt` will have a margin-bottom
	// in effect.
	> dt:not(:first-child) {
	margin-top: -1rem;
	}
	}

But that assumes we have one "code object" per HTML page. We somehow need to handle multiple code objects, specifically when there is the [source] button.