text: Title: URLScan
  Body: **User story:** I want to submit a URL to URLScan for analysis.
  
  API reference: https://urlscan.io/docs/api/
  
  **Implementation details**
  - Two stage API: POST call, then wait, then GET report
  - Tracecat is not bounded by the one endpoint per Action constraint
  - Action = function. Prioritize usefulness over purity
  - Use recommend retries and timeouts:
  
  >  The suggested polling logic would be to wait 10-30 seconds directly after submission and then polling in 5-second intervals until the scan is finished or a maximum wait time has been reached.
  
  - There are three `visibility` options: `public`, `private`, `unlisted` (only visible to verified security researchers)
  
  **Key requirements**
  - [x] Can scan URL and return report
  - [x] `private` visibility by default : https://portswigger.net/daily-swig/urlscan-io-api-unwittingly-leaks-sensitive-urls-data
  - [x] Add icon to frontend 
  
  Note: we will NOT implement the [search API](https://urlscan.io/docs/search/) for now. There is a massive set of possible search queries. We need more data from URLScan power users of what searches *actually* matter 