Alignment: Don't require a Connectable base, split.

[dtzSiFive]

No non-internal existing functionality intended to be changed.

"Alignment" interface (internal) does change.

DataMirror methods implemented in terms of Alignment no longer require the Data to be hardware, allowing walking (bare) Chisel types and their alignments.

This will be used in a follow-on PR.

Contributor Checklist

• Did you add Scaladoc to every public function/method?
• Did you add at least one test demonstrating the PR?
  • This PR is meant to only refactor while supporting existing behavior. New functionality will follow.
• Did you delete any extraneous printlns/debugging code?
• Did you specify the type of improvement?
• Did you add appropriate documentation in docs/src?
• Did you request a desired merge strategy?
• Did you add text to be included in the Release Notes for this change?

Type of Improvement

• API modification
• Internal or build-related (includes code refactoring/cleanup)

Desired Merge Strategy

• Squash: The PR will be squashed and merged (choose this if you have no preference).

Release Notes

DataMirror methods relating to alignment such as collectAlignedDeep) no longer require Data to be Hardware and may be used on bare Chisel types.

Reviewer Checklist (only modified by reviewer)

• Did you add the appropriate labels? (Select the most appropriate one based on the "Type of Improvement")
• Did you mark the proper milestone (Bug fix: 3.5.x, 3.6.x, or 5.x depending on impact, API modification or big change: 6.0)?
• Did you review?
• Did you check whether all relevant Contributor checkboxes have been checked?
• Did you do one of the following when ready to merge:
  • Squash: You/ the contributor Enable auto-merge (squash), clean up the commit message, and label with Please Merge.
  • Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

[azidar]

LGTM! Thanks!