Added utility functions to initialize and hold a struct for passing around the RNA info to functions for increased maintainability

[LunarFawn]

There are currently a lot of calls that must be made for every function we have to manipulate the strings coming from TS to C++ or to hold data structures. These clog up the readability of the codebase and make maintainability hard and adding new functions difficult. I created a stuct called SequenceStructureInfo in the Utils class for this. I made 3 functions called setSequenceInfo, setStructureInfo, and setGlobals to initialize values in the struct when appropriate in functions.

setSequenceInfo takes the RNA sequence string as a input by value and then created teh char array that is passed to the folding calls as well as generating the numerical RNA sequence array and recording the sequence length. the function is passed the SequenceStructureInfo struct by reference to make recording quick.

setStructureInfo take the secondary structure string as a input by value and SequenceStructureInfo struct by reference. This function records teh struct string, gets the char array for the structure as well as getting the pairs lists.

setGlobals takes a bool for setting the useMFE and OnlyOneMFE globals as well as the pknot and temp as inputs. It also is passed the SequenceStructureInfo struct by reference. This function sets teh complexity, sets a isPknot bool, as well as records teh folding temp.

The SequenceStructureInfo is called with the dnastucts variable for the ensemble already enumerated and when you are working on a specific single dna stuct from the dnaStructures struct then you assign it to teh oneDnaStruct currentStruct

[luxaritas]

While the simplifications here are good, but I'm concerned that there's a lot of leaky abstractions here - it feels like there's a lot of mixing concerns, side-effects, and implicit assumptions in usage.

We discussed this in more detail via DM - marking as a draft for now