Update chrome extension to make api calls to AWS Lambda using current URL

[sungho-cho]

• Make API calls in background script instead of popup script
  • Currently triggered by popup script only, but can later be triggered by content script as well (HTML Injection)
  • Make calls to AWS API instead of localhost
• Update popup script to send a URL to background script
• Remove code from content script
• Update corresponding types in types.ts

Updates:

• Send failure message instead of url for invalid articles in lambda_function.py
• Handle successful responses differently depending on status code in Popup.tsx
• Use wretch().res() instead of wretch().json() in order to access the response code
• Add empty wretch().error() for TODO PR
• Fix loading wheel error by returning true at the end of message listener (it indicates there will be an asynchronous response)

[sungho-cho]

@chorongi Because, in the future, we might want to make API calls on page load from the content script (without pop up). For instance, users could see automatically generated summary on certain websites (e.g. CNN, Medium, etc.). In that case, we could utilize the wretch call that's already implemented in the background script.