This configuration workflow only setups SlapOS Master related bt5 (not vifib_*)

If no data are set the entry is provided by SlapOS Master.

The REQUEST object stays between tests and can create slightly differences in
running tests selectively or in packs.

Additionaly request non shared partition.

Explicit is better than implicit.

Software Instance have no connection_xml, as they are "just requested".

As interaction is called early it can now miss the aggregate setup, so it
have to be caught explicitly.

Software Instance have no connection_xml, as they are "just requested".

Slapos_cache include Shacache implementation on Slapos Master, making it also a shacache provider.
The configuraiton was moved from vifib_erp5 to slapos_cache bt5.

On Tests, Includes slapos_cache and reorganise order of bt5 in order to respecting the auromatic, dependencies handling.