Refactor component and add additional features

[winklerj]

What's Changed

• We've refactored the code to properly use axios and the new message structure
• The unit tests were broken and should now pass
• Added 2 types of pagination (see below)
• Added the ability to rebound based on a JSONata expression applied to the response. For example if you are checking a status in the response or whether a resource exists (which isn't reflected in the status code with a 404)
• Added backwards compatibility between Ferryman 1.7.x and 2.0.0 based on presence of environment variable used for rebound
• REST component now handles all the authentication types available in the secret service
• Ability to override the http response codes to rebound on
• Ability to apply a JSONata transformation to the response body and store in the snapshot. This can be useful for paging scenarios
• Ability to emit the incoming message along with the response
• Ability to retrieve assets from the attachment storage and put downloaded assets into the attachment storage service

Pagination
For the pagination we added two types with the thought to eventually support more.

1. Polling each page using the snapshot as suggested by elastic.io https://docs.elastic.io/developers/how-to-implement-the-pagination.html
2. Looping through all pages in one execution of a REST component step

The difference is that #1 allows a consistent flow of data and you can adjust the interval and page size. #2 allows a flow creator to better reason about how they are consuming data and allows closer to real-time syncing.
Right now we are supporting pagination that exists in the URL and in the body. As an example we are using pagination as a URL parameter and Shopify uses a cursor in the body of the GraphQL request

[SvenHoeffler]

A good number of fixes and enhancements. I currently see no issue adding them.