Refactor the extension code base with async/await API

[RedMickey]

As for now the extension mostly uses chains of bare Promises for asynchronous functions. Migration to async/await API will allow to improve the readability of the code.
Since the extension has a large code base, I think we can try to divide the work by the folders in the extension code base as pointed below.
Progress:

• Migration to async/await API
  • Migration to async/await API in src/common/node folder
  • Migration to async/await API in src/common folder
  • Migration to async/await API in src/debugger folder
  • Migration to async/await API in src/extension folder
    • extension/android folder
    • extension/debuggingConfiguration folder
    • extension/experimentService folder
    • extension/exponent folder
    • extension/ios folder
    • extension/log folder
    • extension/macos folder
    • extension/networkInspector folder
    • extension/windows folder
  • Migration to async/await API in test folder