Divide OligoAttributes into two classes

[lisa-sousa]

I would have two classes here: OligoAttributesCalculator (with the private functions) and OligoDatabaseAttributes which apply the functions to the database. The second one can have a common _apply_calculation(self, calc_function, **kwargs) function which iterates over the oligos and assigns attributes (with dynamic checks). The functions can also be static there

Originally posted by @IsraMekki0 in #51 (comment)

[lisa-sousa]

Additional improvement: parallelize the computation of oligo attributes for a database object.

[lisa-sousa]

Would be good to have a connection to the oligo database such that we don'z have to always instantiate the OligoAttributes class and then call it, e.g. maybe in the same way we get oligo attribute values, e.g. calculate_oligo_attributes(attribute_name, region_ids)? And then check if this oligo attribute can be computed. MAybe the same way as we do the sequence type checks?

[lisa-sousa]

Add parallelization where it makes sense in the database processing/manipulation