v0.8.0: Library Rewrite

[ewang2002]

This PR significantly restructures the library for more flexibility. Some major changes are highlighted below:

• Users can now use the WebRegWrapperBuilder to build a new WebRegWrapper. You'll need to specify the term and cookies, but everything else (client, timeout, user agent) will assume default values.
• The WebRegWrapper structure won't directly support making requests to endpoints that require a term. Instead, users will need to call WebRegWrapper::make_request() to create a builder instance, or WebRegWrapper::default_request() to create a new request instance that can be used to create requests to WebReg endpoints.
  • The builder is there so that users can make requests that might require overriding a value (e.g., if the wrapper's default term is FA23 but you want to make a one-time request for SP23, you can now do this without needing to create a new WebRegWrapper object).
  • Currently, you can override the term, cookies, user agent, timeout, and even the client.
• Separated calling the endpoint from parsing the endpoint's result so we can run tests on the endpoint's result.

Soon

• Support added for getting raw JSON results from WebReg; this might be useful if, for example, you want to do your own processing on the raw JSON instead of having the library do it for you.

---

To Be Completed

• For requests that require a term, separate functions that makes requests with functions that process responses.
• Add ability to make requests and return the string representation of those requests (i.e., no further processing).
• Use cargo's feature gate to give users the ability to enable or disable the wrapper (if the wrapper is disabled, make sure they can still access the parse functions and associated types). For a later release.