Update Readme/Credits, Initial Wyze Lock Support

[coledeb]

List of changes made in this pull request:

• Used @normana10's pull request on @misenhower's original project to introduce initial Wyze Lock support.
• Updated Readme to add the Wyze Lock to list of supported devices, updated credits section to ensure clarity and not require a continuously growing list of separate entries at the bottom.
• Bumped version to 0.5.7 and made necessary Changelog updates.

I personally have not been able to test the Wyze Lock functionality, as I do not own a Wyze Lock. User u/nsh02 on the Homebridge subreddit, who has been using my previously created fork/pull request, confirmed that their Wyze Lock is now able to be seen, as well as actioned on after testing this version. I can confirm that I do not see any changed/broken functionality or newly introduced errors in my personal use of this version (sans Wyze Lock of course).

[coledeb]

@connorgallopo I tested your proposed fix of replacing the value of HOMEKIT_COLOR_TEMP_MIN with 638 in WyzeMeshLight.js to fix the 'Color Temperature' warnings, however, this introduced errors when I tried running this on my personal Homebridge install. I had no errors when changing colors on bulbs prior to testing that fix, and after testing/updating it generated several near-identical errors (an example included below):

[8/6/2021, 9:38:42 PM] [homebridge-wyze-connected-home-op] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 511 exceeded maximum of 500. See https://git.io/JtMGR for more info.

As a result, I did not include this in the pull request. I am not an adept programmer, so I am not exactly sure what would be causing those errors for you, or how to resolve them myself.

[coledeb]

Closing because of further updates