Use `StaticInteger`s instead of `Tuple{1,2,3}` in `StaticArray` type parameter?

StaticArray uses Tuple{1,2,3} to encode the size:

https://github.com/JuliaArrays/StaticArrays.jl/blob/cee335d3e7f08dcc72075ac5f18bb3a632e8b841/src/StaticArrays.jl#L73-L76

Arguably, the type parameters of Tuple should be types. Otherwise, such Tuple does not have an instance. It also confuses some users (including me when I first saw this): What does Tuple{3} mean in StaticArrays? - Usage / First steps - JuliaLang.

A better solution may be to use Tuple{StaticInteger{1},StaticInteger{2},StaticInteger{3}} instead of Tuple{1,2,3}. For example, a possible implementation of SArray would be

struct SArray{N, S <: NTuple{N,StaticInteger}, T, L} <: StaticArray{S, T, N}
    data::NTuple{L,T}
    size::S
end

const SVector{S, T} = SArray{1, Tuple{StaticInteger{S}}, T, S}
const SMatrix{S1, S2, T, L} = SArray{2, Tuple{StaticInteger{S1}, StaticInteger{S2}}, T, L}

(Early discussion in https://github.com/JuliaArrays/StaticArrays.jl/issues/806#issuecomment-655279036)

Read src/StaticArrays.jl at lines 73-76, then review the early discussion in issue #806 and the linked Julia Discourse thread. Compare the current Tuple-based size parameters with the proposed StaticInteger representation and determine whether the design is acceptable. Done requires an agreed representation and consistent implementation of the affected StaticArray types.