[Feature Request] Expose Advertising Timeout

[Philedor]

Hi Everyone,

I was working on an oldish linux system (buster, bluez 5.50) and could for the life of me not get stable advertising. Turns out for some reason in my system this assumption was not valid/working:

bluetooth/gap_linux.go

Lines 117 to 122 in 5c61529

	// The documentation states:
	// > Timeout of the advertisement in seconds. This defines the
	// > lifetime of the advertisement.
	// however, the value 0 also works, and presumably means "no
	// timeout".
	"Timeout": {Value: uint16(0)},

After I ran a local vendor copy and changed that value, I was advertising without any problems at all. Would it be possible to expose this timeout option in the AdvertisementOptions?

I was hesitant to create this issue given this previous issue but changing scanning mode changed nothing for me. Additionally, I had different bluetoothd log behaviour:

bluetoothd[6980]: src/advertising.c:client_create() Adding proxy for /org/tinygo/bluetooth/advertisement1
bluetoothd[6980]: src/advertising.c:register_advertisement() Registered advertisement at path /org/tinygo/bluetooth/advertisement1
bluetoothd[6980]: src/advertising.c:refresh_adv() Refreshing advertisement: /org/tinygo/bluetooth/advertisement1
bluetoothd[6980]: src/advertising.c:client_timeout()
bluetoothd[6980]: src/advertising.c:client_release() Releasing advertisement :1.135, /org/tinygo/bluetooth/advertisement1

It's probably a rare case, but I was not planning on diving this deep into it all when I started. Maybe an exposed Timeout Option would point someone else with my issue in the right direction.

Thanks for considering!