Add SelectionOptions type and refactor GetThermostat to use them

[cvvs]

I wanted to be able to configure GetThemostat selection data, and you have a TODO to allow for this, so I created a SelectionOption type which can be passed into GetThermostat to set specific selection options when making a request.

I modified the GetThermostat to take the options as a variadic parameter, so the change should be backwards compatible.

Originally, the option funcs were all With<SettingName> but that seemed redundant, so removed the With.

I can undo the formatting changes made by gofmt if you prefer.

[rspier]

Sorry for the delayed review, April and early May were something special...

Anyway, thank you for the PR. A few very minor tweaks if you don't mind...

Originally, the option funcs were all With but that seemed redundant, so removed the With.

I agree the With is providing much value, but the option func pattern generally uses it, so in the name of consistency, maybe add them back? (Or you could probably convince me I'm being silly about that.)

I can undo the formatting changes made by gofmt if you prefer.

Yes please. I'm not opposed to the changes, but let's make them outside the scope of this PR. Also, what version of gofmt are you using? 1.22 isn't making those changes for me.

[cvvs]

I'll try to get the requested changes done as soon as I get some spare dev time.

[rspier]

Merged, thank you!

In hindsight, I wonder if we should have just done WithSelection(*Selection)? as a GetThermostatOption func?

[cvvs]

Funny you should say that. I was working on a mock http client this week, and after writing way too many option funcs, I ended up doing something similar with *http.Request. Had I done this this weekend, I probably would have done what you suggested.

[rspier]

It's not too late to change our mind and switch the interface.

I figure we can retain a default Selection for the common case, but anyone who wants something special can specify all the fields they care about.