[Method Browser] Refactoring command migration

[AlexisCnockaert]

Start of refactoring commands migration from Calypso to Spec !
This is a good setup in order to use them for the MethodBrowser ( not for playground or anything else yet, we need to provide a unified API so the commands don't raise errors).
If there are broken tests it may be because the command classes need to be merged in Spec repository.
(all failing tests will pass when pharo-spec/Spec#1892 will be merged)

[Ducasse]

oops there is a conflict

[AlexisCnockaert]

It is fixed!

[Ducasse]

Strange I see

StMethodBrowserTest
 ✗ #testExplicitBrowseClassNameAsLiteral (9ms)
 ✗ #testRefreshingBlockWithLiteralString (90ms)
 ✗ #testOpenWithoutMessageShouldNotDNU (61ms)
 ✗ #testExplicitBrowseCompiledMethods (5ms)
 ✗ #testHandleMethodModifiedRemovesSenderWhenNoLongerMatching (97ms)
 ✗ #testHandleMethodRemovedUpdatesSelection (13ms)
 ✗ #testBrowseClassNameAsLiteral (180ms)
 ✗ #testExplicitBrowseSenders (2ms)
 ✗ #testMethodBrowserImplementors (12ms)
 ✗ #testHandleMethodAddedAddsMatchingSender (88ms)
 ✗ #testBrowseReferencesToVariableInClass (3ms)
 ✗ #testExplicitBrowseClassNameAsClass (2ms)
 ✗ #testWindowTitleWithFilterRatio (89ms)
 ✗ #testHandleMethodRemovedRemovesMatchingMethod (12ms)
 ✗ #testBrowseClassNameAsClass (86ms)
 ✗ #testExplicitBrowseImplementors (3ms)
 ✗ #testMethodBrowserSenders (9ms)

[AlexisCnockaert]

@Ducasse it is linked to Esteban changes with the new SpCodeEditorPresenter

[AlexisCnockaert]

I fixed everything normally, all failing tests need pharo-spec/Spec#1892 to be merged