fix(display): correct module trigger logic and ensure header visibility

[dfl-aeb]

Fix: Module Trigger Logic and Header Visibility

Problem:

• Module headers were incorrectly displayed even when the module itself was supposed to be hidden by the moduleTriggerTemplate. This led to overlapping headers in the user interface.

• There was a typo in the configuration option (useModuleTigger instead of useModuleTrigger).

Solution:

This PR addresses the issues mentioned above with the following changes:

1. Corrected Header Visibility: The getHeader function in MMM-HomeAssistantDisplay.js has been adjusted to return null (and thus render no header) when the module is hidden via useModuleTrigger (or useModuleTigger).
2. Typo Correction: The typo useModuleTigger has been corrected to useModuleTrigger throughout the module file (MMM-HomeAssistantDisplay.js).
3. Backward Compatibility: To avoid breaking existing configurations, backward compatibility for the misspelled useModuleTigger option has been implemented. The module now checks for both spellings (useModuleTrigger || useModuleTigger).

Impact:

• Hidden modules will now correctly no longer display their headers, resolving the issue of overlapping headers.
• The configuration is now more consistent due to the typo correction.
• Existing configurations using the useModuleTigger typo will continue to work without requiring modification.

[Copilot]

Pull Request Overview

This PR fixes display issues in the MMM-HomeAssistantDisplay module by correcting module trigger logic and ensuring proper header visibility control. The changes address overlapping headers when modules should be hidden and fix a configuration option typo.

• Corrected typo from useModuleTigger to useModuleTrigger while maintaining backward compatibility
• Fixed header visibility logic to hide headers when modules are triggered to be hidden
• Updated trigger condition checks throughout the module to use corrected logic

[Copilot]

The comment maintains the intentional misspelling 'Tigger' for backward compatibility, but it should clarify that this is a deprecated option. Consider updating the comment to: '// For backwards compatibility - deprecated, use useModuleTrigger instead'

Suggested change

	useModuleTigger: false, // For backwards compatibility
	useModuleTigger: false, // For backwards compatibility - deprecated, use useModuleTrigger instead

[Copilot]

The condition checks !this.displayModule but displayModule is not defined or initialized in the visible code. This could result in the header always being hidden if displayModule is undefined. Ensure displayModule is properly initialized and updated based on the module trigger logic.