fix: handle decimal-formatted integers in date parsing

[rukayaj]

• Replace Integer.parseInt with NumberUtils.parseInt to handle decimal-formatted integers (e.g., "29.0" → 29) in date components
• Affects Runner, LocalDateInterval, LocalDateTimeInterval, and DwCOtherDateDQ
• Maintains TG2 compliance by accepting only unambiguous integer values
• Fixes NumberFormatException errors when parsing dates with ".0" suffixes

I'm aiming to allow parsing date components that are stored as decimals while still rejecting true non-integer values, aligning with TG2 spec requirements for "interpretable as integer" fields.