Make it easier to collect info for new devices

[make-all]

Description

Now that an iot.tuya.com account is no longer needed to get local keys, users do not have a good source of info for dps info for new devices. This has led to a regression in quality of reports, which often don't contain the needed enum/integer range info, and sometimes not even dp ids, making the report useless.

Steps to reproduce

1. Login with QR code method
2. Try to add a device which is unsupported
3. Try to gather what info you can without a Tuya developer account

Expected behaviour

Now that cloud functionality is available, we could try to pull in all the info needed and log it, so we just need to send users to the log file for gathering info.

Additional context

No response

Confirmation

• [X] I am sure this is a bug, or improvement that is well enough described that it can be implemented

• [x] If this is for a specific device, the device config is mentioned above, or diagnostics are included.

• [X] This is not requesting addition of a new device

[make-all]

Unfortunately the QR code login does not appear to give full access to the iot core API functions. There are errors coming back from the API about invalid "app" parameter - the app parameter requires a registered app, which is the iot.tuya.com signup process, the QR code login is an authorisation to access the user account from the Tuya branded app, but does not transmit the app code.