Create script to launch clive in docker with reasonable options

Launching a clive should support 2 modes:

• TUI
• starting cli environment ready for direct usage of clive cli commands

1. TUI: start-clive.sh having options:

• --data-dir=path which points directory where clive like also internally started beekeeper holds store data (i.e. profile, encrypted keys). Path should be optional and by default point to ${HOME}/.clive directory
• all other options should be directly passed to spawned TUI

2. CLI: clive.sh having options:

• --data-dir=path (same as TUI version)
• --exec=path optionally taking a bash script to be executed inside CLI environment
• all other passed arguments should be directly passed to internally started clive process

To simplify usage, internally started docker container should have mapped absolute path ( from host pwd ) what should allow to use same paths inside docker as on host machine.

Started CLI environment should print basic usage information (i.e. text to explain how to get help on available commands). Also printed prompt should contain information about activated clive environment and selected profile.

Activated environment should take care for spawning a beekeeper tool which should be working until cli environment will be explicitly closed. Additionally, environment setup should create a session to beekeeper and hold a communication token inside local environment variable to allow communication between beekeeper and clive commands without a need to specify a password each time and opening explicit session each time