Bluetooth: Controller: Fix minimal Kconfig depends and defaults

Fix default value of BT_TICKER_REMAINDER_GET, it will be
selected based on enabled Controller features. This is not
needed by minimal peripheral role.

Fix depends on for BT_CTLR_CONN_RANDOM_FORCE as it is
applicable when more than one simultaneous connections is
supported. Again, this is not needed by minimal peripheral
role.

Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>

Author: cvinayak

subsys/bluetooth/controller/Kconfig.ll_sw_split

@@ -1126,7 +1126,7 @@ config BT_CTLR_FORCE_MD_AUTO
 
 config BT_CTLR_CONN_RANDOM_FORCE
 	bool "Random forced scheduling for peripheral on missed anchor point"
-	depends on BT_PERIPHERAL
+	depends on BT_PERIPHERAL && (BT_MAX_CONN > 1)
 	default y
 	help
 	  When enabled, controller will have legacy behavior and randomly force
@@ -1259,7 +1259,6 @@ config BT_TICKER_REMAINDER_GET
 	depends on BT_TICKER_REMAINDER_SUPPORT
 	select BT_TICKER_NEXT_SLOT_GET
 	select BT_TICKER_NEXT_SLOT_GET_MATCH
-	default y
 	help
 	  This option enables ticker interface to iterate through active
 	  ticker nodes, returning tick to expire and remainder from a reference