Closes #2432 - Revert SegArray to Client Side

[Ethan-DeBandi99]

Closes #2432

This code "reverts" SegArray to a client only implementation. This required some modification to maintain functionality that was added that took advantage of the SegArraySymEntry. This implementation should provide more flexibility moving forward and relieve some memory pressure that could be caused by the Server side implementation.

• Deprecates ak.segarray and ak.SegArray.from_parts. These will be maintained for at least 1 release cycle with deprecation warnings.
• Updates the __init__ method to take in segments and values with lengths and grouping as optional parameters
• Moves SegArray indexing code back to the client. The client side implementation also prevents duplicate arrays from being generated on the server. This should alleviate some memory pressure. If users desire we can add a flag to allow them to create copies when generating the SegArray in order to maintain the original objects used for creation.
• Updates SegArray related IO workflows to account for there no longer being a SegArray server object. These are now handled as a segments and values array.
• Updates message configuration to send SegArray objects as {"segments": segarray.segments.name, "values": segarray.values.name}. Server side workflows updated where applicable.
• Register/attach code updated. Only segments and values are registered now. This prevents storage of 2 additional objects that can be recomputed on attach.
• src/SegmentedArray.chpl Deleted
• SegArraySymEntry class removed

[stress-tess]

Couple of things to look at. The only big one is registration is gonna need a bit of reworking

[stress-tess]

Looks good!

[hokiegeek2]

just a couple comments re: slots