CHAD-13777 Allow virtual device events to not always be a state change

[greens]

Adds a new certified preference 'forceStateChange' that allows users to select whether they want their virtual device events to always be a state change or not.

Check all that apply

Type of Change

• WWST Certification Request
  • If this is your first time contributing code:
    • I have reviewed the README.md file
    • I have reviewed the CODE_OF_CONDUCT.md file
    • I have signed the CLA
  • I plan on entering a WWST Certification Request or have entered a request through the WWST Certification console at developer.smartthings.com
• Bug fix
• New feature
• Refactor

Checklist

• I have performed a self-review of my code
• I have commented my code in hard-to-understand areas
• I have verified my changes by testing with a device or have communicated a plan for testing
• I am adding new behavior, such as adding a sub-driver, and have added and run new unit tests to cover the new behavior

Description of Change

Summary of Completed Tests

[github-actions]

Duplicate profile check: Passed - no duplicate profiles detected.

[github-actions]

Test Results

   62 files  ±0    383 suites  ±0   0s ⏱️ ±0s
1 863 tests +1  1 863 ✅ +1  0 💤 ±0  0 ❌ ±0 
3 250 runs  +1  3 250 ✅ +1  0 💤 ±0  0 ❌ ±0 

Results for commit 13fa587. ± Comparison against base commit 0706571.

[github-actions]

File	Coverage
All files	100%	✅

Minimum allowed coverage is 90%

Generated by 🐒 cobertura-action against 13fa587

[kdbang]

sorry for late.
looks good to me.