sumCountIf and sumCountDistinct serialization compatibilityafter Nullable(Tuple) introduction (follow-up to #97502)

[zlareb1]

Describe what's wrong

• PR Fix sumCount aggregate function not being able to read older serialized states after introduction of Nullable(Tuple) #97502 fixed sumCount serialization compatibility after the Nullable(Tuple) introduction.
• The same fix was not applied to sumCountIf and sumCountDistinct.
• Users with AggregatingMergeTree data using these functions with Nullable arguments will get errors reading stored states.

Does it reproduce on the most recent release?

Yes

How to reproduce

Verified post #97502 merge:

  -- sumCountIf: old state fails
  SELECT finalizeAggregation(CAST(
      unhex('0A0000000000000004'),
      'AggregateFunction(sumCountIf, Nullable(UInt8), UInt8)'
  ));
Received exception:
Code: 32. DB::Exception: Attempt to read after eof: In scope SELECT finalizeAggregation(CAST(unhex('0A0000000000000004'), 'AggregateFunction(sumCountIf, Nullable(UInt8), UInt8)')). (ATTEMPT_TO_READ_AFTER_EOF)

  -- sumCountDistinct: old state fails
  SELECT finalizeAggregation(CAST(
      unhex('03000201'),
      'AggregateFunction(sumCountDistinct, Nullable(UInt8))'
  ));
Received exception:
Code: 36. DB::Exception: AggregateFunction state for `sumCountDistinct` has 2 trailing byte(s) after deserialization: In scope SELECT finalizeAggregation(CAST(unhex('03000201'), 'AggregateFunction(sumCountDistinct, Nullable(UInt8))')). (BAD_ARGUMENTS)

  -- sumCount IS fixed for reference:
  SELECT finalizeAggregation(CAST(
      unhex('0A0000000000000004'),
      'AggregateFunction(sumCount, Nullable(UInt8))'
  ));
  -- (10,4) ✓