[testing] Move D/I Mem tests to MemorySpec

[adkian-sifive]

In anticipation of Scala 3 D/I

Contributor Checklist

• Did you add Scaladoc to every public function/method?
• Did you add at least one test demonstrating the PR?
• 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

• 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

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.6.x, 5.x, or 6.x depending on impact, API modification or big change: 7.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) and clean up the commit message.
  • Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

[jackkoenig]

Why should these be moved?

[adkian-sifive]

SRAM library depends on D/I so we can't support that in Scala 3 until D/I is implemented. We can't move D/I tests until this is out of it

[jackkoenig]

SRAM library depends on D/I so we can't support that in Scala 3 until D/I is implemented. We can't move D/I tests until this is out of it

But you can't move the D/I tests until D/I is implemented anyway right?

[adkian-sifive]

Yeah but then I can't move D/I tests until SRAM is also implemented, which will be a separate patch after

[adkian-sifive]

Ok so my plan was to move D/I with its tests together in the same patch, which is how I've been doing major feature PRs for Scala 3. But now that I think about it that's going to be quite a lot of work for D/I because of all this intermixing in its testing. What I can do instead is to make PRs for everything before moving any of the tests