Add HtSP, HtSS, HtSU, SetS

[pelijah]

Your checklist for this pull request

• I've read the guidelines for contributing to this repository
• I made sure to follow the project's coding style
• I've documented or updated the documentation of every function and struct this PR changes. If not so I've explained why.
• I've added tests that prove my fix is effective or that my feature works (if possible)
• I've updated the rizin book with the relevant information (if needed)

Detailed description

• All ht_*_new0() are removed
• freefn field of HT options was renamed to finiKV
• finiKV_user fields was added to HT options
• Added ht_*_new_opt_size API
• HtSP and HtUP are created with ValueFree callback that allows to reduce extra LOC and prevent bugs
• SetP replaced with SetS (based on HtSP)
• rz_th_ht_*_new0() and rz_th_ht_*_new_opt() are replaced with rz_th_ht_*_new(HtXX *)

[XVilka]

I suppose it is to address #4261 ?

Overall I agree with the change but not sure if names of new functions are good ones. It's not clear what they are supposed to do just from the name, IMHO.

Also, since many of the calls use default arguments, what about creating a wrapper called something like ht_..._new_default_opts()?

@ret2libc please take a look at this PR.

[ret2libc]

The PR looks good overall, I'll do a full review once it's ready for review. I agree however the names might not be ideal... 1) i think we should add some explanation for all existing ht (or at least this new ones) 2) instead of s2p/s2s we should use sp, ss because the others are called uu, pp, etc.

[Rot127]

Would do a full review when it is ready as well. Also agree with ret2libc and xvilka when it comes to the naming.

[pelijah]

instead of s2p/s2s we should use sp, ss because the others are called uu, pp, etc.

@ret2libc Do you mean to replace 'HtPP * ht_pp_new_s2p()' with 'HtPP * ht_sp_new()' or to add a whole bunch of HtSP API? The second one seems not less confusing because HtSP still be HtPP. Not to mention HtSS.