Use Status Code or golang variables

[laurentsenta]

@hacdias raised a want to use http.StatusMovedPermanently instead of raw status code like 301
#58 (comment)

Creating an issue here to agree & then rename all the status code in a single PR if we want too.

[laurentsenta]

I'm neutral:

• named variables are more readable
• but when you have an error in your tests, status code is 200, expected 301, it's easier to search for raw numbers in your codebase.

[laurentsenta]

cc @lidel @galargh

[galargh]

I think we should do what's easier for test maintainers. Personally, I can go either way. One thing I'm wondering about - how do we refer to exit codes in spec? If it's only by numbers, then it might be slightly more straightforward for test writers to keep using numbers in gateway conformance too.

[hacdias]

@galargh in the specification itself we do things like 404 Not Found. We always say the "{ Number } { Text }" AFAIK.