Move SegArray to Server

[Ethan-DeBandi99]

SegArray is currently a client side construct that keeps track of several pdarray objects to manage its elements. This is very similar to ak.String which is currently referred to as SegString/SegArray on the server. This will eventually be transitioned to SegString on the server entirely as it will most likely inherit functionality from the SegArray module.

This issue is to serve as an overall tracking issue for the transition.

• Move SegArray Object from Python to Chapel (Move SegArray to Chapel Module #1571)
• Move/Configure all SegArray functionality in Chapel (Move SegArray.__init__ fully to server #1681 & Move SegArray functionality to server #1682)
• Update naming of SegString (currently SegArray) on the server (Rename SegmentedArray to SegmentedString #1574)
• Configure SegString to inherit from SegArray to utilize the shared functionality. (EDIT: This may not be done because there are some fundamental differences between these 2 objects that could cause problems.)

[stress-tess]

I wanted to link this PR where we first added SegString as a standalone object in chapel (vs two pdarrays that we logically treated as related)

I'm not sure how useful it will be but the PR description should give a good reference for our Hierarchy (CompositeSymEntry is where this would go i'm guessing). And maybe src/MultiTypeSymEntry.chpl will provide an example of sorts?

[Ethan-DeBandi99]

The SegArray server side implementation has been reverted to client side only due to functionality limitations due to the server side implementation. Closing issue.