Fixing hassfest validation

[srkoster]

I noticed that my previous PRs failed the hassfest validation on existing code. This change should bring that code in line with the hassfest checks.

Error: R] [DEPENDENCIES] Using component tag but it's not in 'dependencies' or 'after_dependencies'

• Fixed in manifest.json by adding tag to after_dependencies. It was triggered because of from homeassistant.components.tag import async_scan_tag in __init__.py. Added the after_dependencies makes sure that the home assistant tag component is loaded before the Dahua integration.
• Also reordered the fields in manifest.json as "Manifest keys should be sorted: domain, name, then alphabetical order"

Error: R] [SERVICES] Service set_infrared_mode has a field mode with no name and is not in the translations file
Error: R] [SERVICES] Service set_infrared_mode has a field brightness with no name and is not in the translations file
Error: R] [SERVICES] Service set_video_profile_mode has a field mode with no name and is not in the translations file
Error: R] [SERVICES] Service set_video_in_day_night_mode has a field config_type with no name and is not in the translations file
Error: R] [SERVICES] Service set_video_in_day_night_mode has a field mode with no name and is not in the translations file
Error: R] [SERVICES] Service set_record_mode has a field mode with no name and is not in the translations file

• Fixed in services.yaml by adding a name attribute to the mentioned fields.

Warning: G] [CONFIG_SCHEMA] Integrations which implement 'async_setup' or 'setup' must define either 'CONFIG_SCHEMA', 'PLATFORM_SCHEMA' or 'PLATFORM_SCHEMA_BASE'. If the integration has no configuration parameters, can only be set up from platforms or can only be set up from config entries, one of the helpers cv.empty_config_schema, cv.platform_only_config_schema or cv.config_entry_only_config_schema can be used.

• Fixed in __init__.py by removing async_setup as its not implemented and YAML setup is not supported

[rroller]

Thanks again!