Fix double support: Parse actual numeric values instead of returning hardcoded 0/0.0

[ikku47]

Problem

The FlutterJsonBeanFactory plugin had broken double support because the MapTypeAdapter.read() method in GsonUtil.kt was returning hardcoded values (0 for integers, 0.0 for doubles) instead of parsing the actual JSON numeric values.

This meant that all numbers in JSON were being replaced with either 0 or 0.0, completely breaking the double support functionality.

Solution

• Fixed MapTypeAdapter.read() to parse and return actual numeric values using dbNum.toLong() and dbNum.toDouble()
• Maintained proper error handling with fallback to 0/0.0 only when parsing fails
• Added .intellijPlatform to .gitignore as recommended by the build system

Changes

• GsonUtil.kt: Fixed number parsing logic in MapTypeAdapter.read() method (lines 117-137)
• .gitignore: Added .intellijPlatform directory

Testing

The fix ensures that:

• ✅ JSON numbers like 3.14159 are preserved as 3.14159 (not 0.0)
• ✅ JSON integers like 42 are preserved as 42 (not 0)
• ✅ Type detection continues to work correctly
• ✅ Error handling is maintained

Before/After

Before: All JSON numbers → 0 or 0.0
After: JSON numbers → actual parsed values with correct types

Root Cause

The original code was a placeholder implementation that correctly identified number types but forgot to actually parse and return the real values. This was likely an oversight during development where the type detection logic was implemented but the value parsing was left as hardcoded placeholders.