Do not give StringVectors to users

[jakobnissen]

A StringVector v is a Vector{UInt8} which wraps memory allocated as a string. This allows String(v) to be zero-copy which is good for performance. However, if users are handed a StringVector directly, they can use that to unknowingly mutate strings, which is illegal.
For example, suppose a user calls a function f which returns a StringVector v. They can then do the following to mutate a string s:

v = fill!(Base.StringVector(3), 0x00);
v2 = reshape(v, 3, 1)
s = String(v) # all zeros
v2[1] = 0x01
s

The solution in this PR is to not ever let StringVectors escape out to the user, by instead returning normal Vector{UInt8} from the functions that would otherwise do so.

For reviewers

Potential solution to #54434
Alternative to #54424

Still needs to be rebased on top of #54372 before merging, as these two PRs overlap quite a bit

[KristofferC]

This seems a bit strange since StringVectors seem to be particularly made to be used in IOBuffer:

julia/base/iobuffer.jl

Lines 43 to 45 in bbae417

	# allocate Vector{UInt8}s for IOBuffer storage that can efficiently become Strings
	StringMemory(n::Integer) = unsafe_wrap(Memory{UInt8}, _string_n(n))
	StringVector(n::Integer) = view(StringMemory(n), 1:n)::Vector{UInt8}

[KristofferC]

I would say same thing as applied 7 years ago applies now. #24388 (comment)