feat: add CIRCTSRAMInterface

[unlsycn]

This PR provides a wrapper to generate a CIRCT-compatible SRAM, so that we can use it to replace the SRAM in the CIRCT.

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

• Feature (or new API)

Desired Merge Strategy

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

Release Notes

Add CIRCTSRAMInterface

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), 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.

[sequencer]

I like this API(since I originally designed it in our in-house codebase). Should it be CIRCTSRAMInterface or some other better name? I don't know. It follows the the old story when SFC was alive, MFC also follows it. This Module can be the chisel Public version to it, and write some memory behavior model in the future.

In the future, I wanna it can provide additional port MBIST feature.

[sequencer]

LGTM