refactor IsNumericLike and fix UnionMin, UnionMax types

[benzaria]

• refactor: remove unnecessary condition for IsNumericLike that cosed an error and add cases for never/any.
• fix: behavior of UnionMin to UnionMax returning 0 for never , any for number, erroring for any and Infinity.
• add: introduce IsAnyOrNever type alternative for IfNotAnyOrNever. (internal)

Original behavior:

type A = IsNumericLike<'1.2.3'>
//=> true

type T = UnionMax<never>
//=> 0

type T = UnionMax<any>
//=> any // Error: infinite

Current behavior:

type A = IsNumericLike<'1.2.3'>
//=> false

type T = UnionMax<never>
//=> never

type T = UnionMax<any>
//=> any

[benzaria]

Reason to introduce IsAnyOrNever:

type CountTo<T> = count to T;

type Count1<T> = IfNotAnyOrNever<T, CountTo>;
type Count2<T> = IsAnyOrNever<T> extends true ? T : CountTo<T>;

type A = Count1<any>
//       ~~~~~~~~~~
// Error: Type instantiation is excessively deep and possibly infinite.

type B = Count2<any>
//=> any

IMO, IsAnyOrNever is a better alternative and should replace the current implementation of IfNotAnyOrNever. This is because, when using an If-style utility, TypeScript always evaluates both branches. That means even the falsy or undesired branch is computed, which can result in unnecessary work, potential type errors, or wasted computation despite it ultimately being discarded.

[benzaria]

@som-sm should UnionMax return PositiveInfinity for number? I feel its more precise because number do include '+∞' and its the maximum number. the same for UnionMin should return '-∞'. WDYT?

[sindresorhus]

should UnionMax return PositiveInfinity for number? I feel its more precise because number do include '+∞' and its the maximum number. the same for UnionMin should return '-∞'. WDYT?

I think it should stay number.