Friendly device names for TS0000 by _TZ0000_abcdefgh

[amis92]

Checklist

• I have filled out the template to the best of my ability.
• This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
• This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.

First of all, thank you for such a great integration, and wow the battery/device submission workflow provides a really great contributing experience!

It came up because I contributed some new devices configs:

• Device: _TZE200_nnrfa68v - TS0601 #3120
• Device: _TZ3000_lbtpiody - TS0201 #3122
• Device: _TZ3000_6km7djcm - TS0041 #3124
• Device: LUMI - lumi.remote.cagl02 #3126

And while I did include a friendly/product/branding name in the issue title, it got renamed to the model/manufacturer values (which is fine), but as a result the "market" name (at least one of them) was lost in the issue change events.

Describe the solution you'd like

I'd love to be able to see some friendly names/example brandings of the nameless tuya/chinese origin. There was a discussion about _TZ/TS devices in #190 but in a bit different topic. So, I'd like to suggest adding a new optional field like "branding_name(s)"/"friendly_name(s)" so that there's at least a chance to find the product in google or compare with other databases etc. Or some other field that would allow adding that kind of value.

Describe alternatives you've considered

It's informative and non-critical, so just leave the db as is, no changes.

Additional context

[andrew-codechimp]

Thanks for the feedback, you actually prompted me to change that description to say it's overwritten automatically and stop people wasting time.

The tuya devices are very strangely named and since I don't own everything in the list I'm relying on contributors to be accurate. I'm not sure what a comment/description would add other than an explainer in the markdown library doc, it wouldn't add any value in the library that's downloaded to the integration and would increase the library size so at this point I don't see myself adding this.