refactor method table handling

[yhteoh]

• Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
  refactor

• What is the current behavior? (You can also link to an open issue here)

• Method table not stateless, it is tracking the time
• MethodTableRegistry not used
• No options class for method tables

• What is the new behavior (if this is a feature change)?

• Moved machine time tracking from method table to vm
• Refactored code to make use of MethodTableRegistry in AnalogInterpreter and AnalogVM
• Moved AnalogVMNULL to oqd_analog_emulator.instructions
• Created MethodTableOptionsBase as base class for options for method tables
• Changed MethodTable run methods arguments from (stack, store, registers) to vm

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
  No

• Other information: