WIP feat: make messenger and protocol inits standalone

[moul]

• delete OpenAccount (sync) and rename OpenAccountWithProgress into OpenAccount
• delete CloseAccount (sync) and rename CloseAccountWithProgress into CloseAccount
• extract the protocol init from OpenAccount into a new OpenProtocol endpoint
• extract the protocol init from CloseAccount into a new CloseProtocol endpoint
• move the NetworkConfig message definition from BertyAccounts to BertyMessenger
• add new errcode.ErrCodes to manage new cases
• update JS code

—-

Note: I considered moving all the NetworkConfig* stuff from BertyAccount to BertyMessenger, but the changes were too big and risky, I prefer to let the JS team refactor this part later, ideally when refactoring the onboarding

My suggestion -> create/import/open account are instant, then, you load the config and decide if you want to ask new prompts (i.e., BLE permission etc), then only you call OpenProtocol with the appropriate configuration

[n0izn0iz]

removing the named return will prevent tyber from catching the correct error

with the named return, a return nil, someErr will set the named return to someErr before executing the defers

that's also why we need to wrap the endSection call in a lambda