Updates to Servo class and fix ESP32 servo issue on beta 55

[brentru]

• Automatically writes min pulse width value to servo object upon creation
  • This removes 1x protobuf data transfer, reduces bandwidth
  • @lorennorman - Please remove the default servo write on staging, let me know here when ready to test.
• Adds getServoIdx for performing index lookup
• Initialize servo struct with default values instead of init'ing within the constructor
• Fixes servo write on ESP32x platforms by using the LEDC timer width from beta 54, instead of the 16bit width from beta 55.

[brentru]

Artifacts are ready for testing + checks passed

[lorennorman]

Only necessary change is the misleading error message, the rest is me having fun.

[lorennorman]

💯

[lorennorman]

@brentru ok this is live on staging for you to test!

[brentru]

@lorennorman Tested on hardware, OK'ing deploy to production

---

Prod

16:27:33.640 > ATTACHED servo w/minPulseWidth: 500 uS and maxPulseWidth: 500uS on pin: 27
16:27:33.648 > -> Servo Attach Response...Published!
16:27:33.917 > * NEW MESSAGE [Topic: Servo]: 
16:27:33.918 > 10 bytes.
16:27:33.918 > Decoding Servo Message...
16:27:33.924 > GOT: Servo Write
16:27:33.924 > Writing pulse width of 500uS to servo on pin#: 27
16:27:33.924 > 27
16:27:34.283 > PING!

Staging

16:32:11.316 > * NEW MESSAGE [Topic: Servo]: 
16:32:11.321 > 15 bytes.
16:32:11.321 > Decoding Servo Message...
16:32:11.327 > GOT: Servo Attach
16:32:11.327 > 27
16:32:11.327 > ATTACHED servo w/minPulseWidth: 500 uS and maxPulseWidth: 500uS on pin: 27
16:32:11.332 > -> Servo Attach Response...Published!

[lorennorman]

@brentru I am wondering if this change has caused "sync" to not do the right thing now, can you test that easily?

To be clear: if there is already a value on the Servo's feed, the device should move to that position on sync (right?) I'm worried I broke this and need a further tweak.

[brentru]

Does not sync on staging