Remove deprecated HashSet from `allergies` tests about elixir HOT 2 CLOSED

Yeah, I guess technically that's correct and we could do that. However, I do like to see some of the less frequently used parts of Elixir used occasionally. After going through all the exercises over the last couple of days I've noticed that someone can make their way through the entirety of the Elixir track on here and not even touch a good chunk of the language. Things like this I think might be helpful in exposing users to new things to check out - in this case, MapSet.

However, since there is a simpler way of expressing this, exposing these language features in this way might be counterproductive. I'm totally open to discussion from others on if we should refactor that in the way you propose, but I think a good first step is just getting rid of the deprecation without refactoring since we know for sure that's gotta go.

from elixir.

I had a quick look, as I didn't recall this exercise had anything to do with sets. It seems we're using sets to ignore order in the lists. Seems simpler to have the helper be something like

def assert_same_elements(actual, expected) do
  assert Enum.sort(actual) == Enum.sort(expected),
         "Expected #{inspect actual} to have the same elements as #{inspect expected}"
end

from elixir.