Parent Requests

Why Ever since launching Insomnia over a year ago, I've received many questions asking "How can I set X for every request", with the most common values for X being headers (#266) and authentication (#330). I knew that eventually I wanted Insomnia to be able to do these things, but was never happy with adding a one-off feature for each, complicating the user experience and forcing the user to learn more things. What Parent Requests (TODO: think of a better name) is a single feature meant to solve the above problem for every possible value of X, by allowing the user to define a request that can be inherited by other requests in a simple and intuitive way. Parent requests... • look similar to a normal request, except that they cannot be sent - doesn't require learning anything new • child requests will show overridden attributes as read-only • list attributes (headers, etc) will be merged (based on name) instead of completely o…