Refactor panama binding and converter framwork

[sequencer]

This PR contains API modifications, but won't affect normal users.

In my original design, I thought the binding framework was trivial, and we may maintain other converter like JNAConverter or JNIConveter, however after 3 months work, I realize I was too native, I don't think it's valuable to devote another intern or master student to work on another implementation. So I removed those abstract deceleration from the main chisel project, to remove the dependency from OM to chiesl.

After this refactor, there are 4 modules to be traced:

• circtpanamabinding is the JavaModule store all CIRCT C-API
• panamalib is the ScalaModule maintaining a internal Scala API for all panama dependencies.
• panamaom is the standalone OMEvaulator, which can be used for parsing mlirbc and providing a Scala API to access all Property generated from Chisel. It won't depend on chisel.
• panamaconverter is the Converter which directly visit the internal ChiselIR, and creating inmemory-MLIRBlock. It is subject to replace the current firrtl serializer in chisel in the future chisel versions. But we may continue maintaining them together in a relative long time.

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)
• API modification
• API deprecation
• Backend code generation
• Performance improvement
• Bugfix
• Documentation or website-related
• Dependency update
• 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).
• Rebase: You will rebase the PR onto master and it will be merged with a merge commit.

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

[sequencer]

Just slip it since it doesn't affect any downstream users(SiFive, UCB, Xiangshan) other than T1, fell free to revert ;p