tools/mcaptest: Seperate disconnect link timeout and call parameters
tools/mcaptest: Seperate disconnect link timeout and call parameters

Data connection shouldn't be automatically closed if MDL disconnect
timeout parameter is given. Disconnect immediately if mdl connection is
established should be triggered with parameter giving and it should be
independent of MDL disconnect timeout parameter. MCL disconnect
possibility (after mdl disconnect) should be also controlled with
parameter independently of its disconnect timeout.

This set of parameters gives possibility to pass all PTS 6.0.1 MCAP test
cases.

ComputeCycles/bluez,silent-snowman/bluez,silent-snowman/bluez,pstglia/external-bluetooth-bluez,mapfau/bluez,silent-snowman/bluez,ComputeCycles/bluez,pkarasev3/bluez,pkarasev3/bluez,pkarasev3/bluez,pkarasev3/bluez,pstglia/external-bluetooth-bluez,mapfau/bluez,mapfau/bluez,mapfau/bluez,ComputeCycles/bluez,ComputeCycles/bluez,pstglia/external-bluetooth-bluez,pstglia/external-bluetooth-bluez,silent-snowman/bluez