Fixing. Registry Reimplementation.

[SerhiiRI]

From the user-perspective

Removed build-compiler
in future releases we'll replace compiler onto the advanced patch system which will be based on Reversed DAG structure passed in secondary time runned execute.

Registry
Registry is now a map-based structure ({:type spec, ...}) instead of a plain vector. registry-create accepts both formats:

;; vector — order = scan priority
(registry-create [from-spec fn-spec])
;; map — explicit keys
(registry-create {:commando/from from-spec, :commando/fn fn-spec})

registry-create support optional key :registry-order in which you may specify in which order need find-command parse items. (Needed in future features). If the user set only two of 5-th used in registry, it mean that explicitely declareted are going first and other just after(and order doesn't metter)
Built registry can be modified with registry-assoc / registry-dissoc without rebuilding from scratch.

From architecture perspective

how registry has been processed before? we took the registry -> injecting internal cmds -> parsing -> ...executing... -> remove external commands from registry. Work practicaly the same but take a look at the current registry structure:

{:registry           {:commando/from {} ...}
 :registry-order     [:commando/from]
 :registry-validated 1772923734358
 :registry-hash      -2017569654}

before passing this registry the parsing procedure we not extending :registy, instead we adding key :registry-runtime which contains _map,_values,_vec at the end of vector. After the execution is done, we removing :registry-runtime.