We need to implement logger based on SLF4J

We need to implement executor with RxJava 1 inside and without android dependency

We need to implement (timber[https://github.com/JakeWharton/timber]) based logger as an available artifact

Sometimes we don't need to get full report but just interested in a state of a bootable.
We need to introduce easy way to know if we are in a current state or just get the state by the means of library.
What is better approach here @Vacxe ?

1. just functions in Boots class
2. package level functions
3. both

Bug report

Describe the bug

• excluded Bootable is executed when it's dependent is not added to exclusion

To Reproduce

Steps to reproduce the behavior:

• Create 2 bootables A, B
• Make A depend on B
• Create Composite Key C which excludes B
• Boot key C
• You will notice B is also booted

Expected behavior

• B should not be booted even if its dependent is not excluded

Screenshots

Currently library outputs too much of unnecessary info to the logging (due to a lot of stuff is dependent on bootables state checks).
Need to rethink what and how we output in the logging info.

As of now, our core artifact coverage is below 60%. We need to improve that to be at least 70%.

Are there plans to support Xamarin.Android (e.g. using xamarin native bindings)?

We need to implement executor with coroutines as it's base (release version of Kotlin 1.3)
This should include 2 bundles: pure Kotlin and with Android support

We need to implement executor that will operate based on handlers (pure Android, no external dependencies)

Implement executor with RxJava 2 inside
That should include 2 versions: core RxJava 2 and RxJava 2 with Android support