[FEA] Variadic ctor parameters

Part of #110 (Refactor of open address data structures)

Development branch: NVIDIA/cuCollections/refactor

Synopsis

To make it convenient to construct a static_set or other data structures with a variety of configuration parameters, we want to use a variadic constructor pattern.

TODOs

• Implement prototype: https://godbolt.org/z/T4oP1nsoW https://godbolt.org/z/Kj763Teon https://godbolt.org/z/5Ghac54E6
• To make this more generic, instead of the get_or_default<T> function looking for a concrete type T, it could look for the first type that satisfies a given concept C, e.g., get_or_default<C>. If necessary, use unique member tags to disambiguate a concept.
• Optional: Ctors that only take a variadic parameter pack (helpful to #101). For this, we need a mechanism to detect if all mandatory parameters are present, e.g., get_or_error<T>.
• refine prototype and fix nvcc build errors: https://godbolt.org/z/5Ghac54E6

References

• https://godbolt.org/z/T4oP1nsoW

Start with the static_set and related data structures named in the issue, then review the linked refactor development branch and the Godbolt prototypes. Confirm which variadic-constructor requirements remain and whether the prototype builds with nvcc. Done means the agreed constructor pattern is implemented and the listed nvcc build issues are resolved.