KP_DashMeter

Feature Updates:
- Added window fade-out functionality:
  - Added three new options in the earance" tab:
    - "Fade out when leaving combat": Window fades out when leaving combat, unchecked by default
    - "Fade out when solo": Window fades out wt in a party, unchecked by default
    - "Fade transparency": Sets the transparency level during fade (default 90%)
- Optimized slider options in the settings in
  - Unified slider width: Height, Width, Spacing, Displacement, Material Height, and Brightness are all changed to double width
  - Adjusted the position of thtness option: Moved from the Color options area to behind the Displacement options
  - Added default value information to tooltips for all slider options (Chinese localization)
- Modified history limi settings:
  - `setslimit` (BOSS records): Default 30, limit 0-30
  - `setstokeep` (Normal combds): Default 15, limit 0-30

Bug Fixes:
- Fixed BOSS recognition issues (Four Horsemen of the Apocalypse 4DK, ObsidSanctum, etc.)
  - Improved ID information in the BOSS database
  - Optimized the isBoss judgment logic, added boss1-boss5 unit detection as a bacp scheme
  - Fixed BOSS death detection logic, supporting multi-target BOSS scenarios
- Fixed the error of the prompt "You are not currently in a party" in random dunge(affects all classes)
  - Modified the party status check logic, no longer using GetRaidRosterInfo (unreliable in cross-realm party scenarios)
  - Chano using UnitName/UnitClass APIs to get party member information, supporting cross-realm parties
  - Fixed multiple party member check logics in Functions.lua, added support RTY_CATEGORY_INSTANCE
- Fixed the issue of duplicate names in death records
  - Added win.actorname = label in the mode_deathlog:Enter function
  - Ensuredplayer names are correctly set in both display modes
- Fixed the issue of confirmation dialogs closing automatically due to timeout
  - Confirmation dialogs for dungeon reset, party join reset, and leave reset will no longer disappear automatically after 30 seconds
  - They will only close after the user clicks the "OK" or "Cancel" button
- Fixed issue of the info bar flickering when fighting a dummy solo due to nearby players in combat
  - Cause: 1) `combat_end` runs `update_timer` after nds, calling `UpdateDisplay(true)` to force UI refresh every second; 2) Event filtering logic has a short time window after the player leaves combat but before actual combat ends to pother people's combat events
  - Fix:
    - Directly cancel `update_timer` in `combat_end` to avoid meaningless timed refreshes after combat ends
  a condition in event handling: ignore other people's combat events when solo and not in combat
    - Optimized `UpdateDisplay` function: Removed the logic to force refrself.current` exists, changed to refresh only when data changes
- Fixed the issue of no prompt when being pulled into a dungeon by a Warlock portal (correctly updated instantatus in the PLAYER_LEAVING_WORLD event)