[SPARK-27653][SQL][FOLLOWUP] Fix since version of min_by/max_by

[dongjoon-hyun]

What changes were proposed in this pull request?

This is a follow-up of #24557 to fix since version.

Why are the changes needed?

This is found during 3.0.0-preview preparation.
The version will be exposed to our SQL document like the following. We had better fix this.

• https://spark.apache.org/docs/latest/api/sql/#array_min

Does this PR introduce any user-facing change?

Yes. It's exposed at DESC FUNCTION EXTENDED SQL command and SQL doc, but this is new at 3.0.0.

How was this patch tested?

Manual.

spark-sql> DESC FUNCTION EXTENDED min_by;
Function: min_by
Class: org.apache.spark.sql.catalyst.expressions.aggregate.MinBy
Usage: min_by(x, y) - Returns the value of `x` associated with the minimum value of `y`.
Extended Usage:
    Examples:
      > SELECT min_by(x, y) FROM VALUES (('a', 10)), (('b', 50)), (('c', 20)) AS tab(x, y);
       a

    Since: 3.0.0

[dongjoon-hyun]

cc @cloud-fan , @viirya , @JoshRosen
Also, cc @jiangxb1987

[dongjoon-hyun]

Thank you for review and approval, @viirya !

[SparkQA]

Test build #112694 has finished for PR 26264 at commit de0f7a9.

• This patch fails Spark unit tests.
• This patch merges cleanly.
• This patch adds no public classes.

[dongjoon-hyun]

The failure is irrelevant to this PR and also it passed all SQL tests.

• KafkaMicroBatchV1SourceSuite.subscribing topic by pattern from earliest offsets (failOnDataLoss: true)

Merged to master.