API server design/creation

[alfiedotwtf]

(Copied over from Gitlab)

This issue incorporates the API server tasks that are required for its initial release

• Use the storage API to read data from the database in the web server
  • Address endpoint TODOs:
    • Add InMemory support for testing
    • Add tests for the address endpoint
    • Add transaction history to the response
    • Add pool support
    • Add account support
    • Add token support to the response
    • Add support for all TxOutput types
• Write tests for the web server based on mocks of the database and ensure the behavior and format is acceptable
• Attempt to store data in postgres from the scanner, and write the config/command line arguments to be used to access the database (host, port, credentials, etc)
• Write the config/command line arguments for configuring the web server to access postgres (host, port, credentials, etc)
• See if we can have a standalone test to write and read data from a docker instance of postgres. This can go into CI
• Figure out the additional required functions, besides the basic ones available now, like get_best_block, to go into the API, and add them one by one
  • Currently there's no way to see all available staking pools with their information to know what to delegate to
• Database tests
  • Create tests that attempt SQL injection attacks on the web API
  • Implement ApiServerStorage for unit tests to force database errors
• We should have a way to list all available staking pools, with information on their offers #1103

[alfiedotwtf]

I've updated the description with the TODOs to get the Address endpoint complete.