Bring in line with latest community standards

[expede]

Credo now warns by default on use of Apply.apply, and piping into anonymous functions. We should consider making these not conflict out of the box.

{Credo.Check.Readability.PipeIntoAnonymousFunctions, false},
# This rule incorrectly flags uses of Witchcraft.Semigroupoid.apply/2
{Credo.Check.Refactor.Apply, false}

See #102 (comment)

[QuinnWilton]

To clarify, Credo specifically warns on cases where apply/2 is used with a list of known size. Credo argues that if you can know the number of arguments at compile time, then you should just call the function directly, with apply/2 being reserved for more dynamic uses.

I agree that finding a way to avoid this warning would be worthwhile though!