[BUG]: Enforce strict FUSE config and mutually exclusive ABI features [LiAuto]

[yangcx000]

Describe the bug

validate-config can return success for unknown FUSE fields, allowing misspelled security-sensitive configuration to fall back to defaults. Separately, fuse2 and fuse3 features can be activated together through Cargo feature unification and silently select one build path.

To Reproduce

1. Add a misspelled field under [fuse] and run validation.
2. Build with both fuse2 and fuse3 enabled.
3. Observe validation/build continue without a clear hard failure.

Expected behavior

Unknown FUSE configuration must fail validation by default, with an explicit compatibility override if required. The build must reject simultaneous ABI features and explicitly handle every feature combination.

OS Version (please complete the following information):

• Linux
• Curvine branch: current main
• Component: config validation and Cargo/build configuration

Additional context

If compatibility review becomes substantial, split this issue into strict config validation and ABI feature exclusivity before implementation.

Test matrix:

• Correct config.
• Unknown field.
• Explicit allow-unknown mode, if retained.
• fuse2 only.
• fuse3 only.
• neither feature.
• both features.