feat(bounty): add report button that append data to a spreadsheet using Rows API

[crocodile-bounty-hunter]

Overview

This PR introduces a significant enhancement to the Help state by integrating user feedback and error reporting with Rows spreadsheet submissions, replacing the previous "Talk to Us" feature. It also automates the setup of necessary configurations using GitHub Actions.

Key Changes

1. Action Replacement and Reporting:

• The "Talk to Us" feature is replaced by an automated submission process to a Rows spreadsheet.
• For pages without detectable tables, a "Report" button logs details (UTC datetime, URL, domain, browser details, and report type) to the spreadsheet.
• A "Report" link is persistently displayed on all pages, allowing users to report issues related to table detection or other concerns via a modal with multiple choices.
  2. Configuration and Automation:
• All necessary Rows API keys are now included in the environment configuration file.
• A new GitHub Action step has been added to automatically generate this configuration file during the release process, ensuring that all settings are correctly applied without manual intervention.

This update aims to streamline user feedback mechanisms and enhance data capture accuracy for better service improvements.

[ricardofelgueiras]

[crocodile-bounty-hunter]

Hey @ricardofelgueiras thanks for you feedback. Regarding the "feedback form".

What do you think about this?

[crocodile-bounty-hunter]

you can test it here.

[ricardofelgueiras]

Hey @ricardofelgueiras thanks for you feedback. Regarding the "feedback form".

What do you think about this?

It's ok.

[ricardofelgueiras]

A few comments on the PR:

• Add the .env file to the .gitignore
• Change the deploy action on the step Build chrome extension dist files and start passing the three env variables via secret. On my side I'll make sure the variables are configured on the repository before you merge it.
• Add a mention to the .env file on the README file explaining why and for what's is being used, and how to set it up when running the extension locally.

Thank you.

[crocodile-bounty-hunter]

A few comments on the PR:

• Add the .env file to the .gitignore
• Change the deploy action on the step Build chrome extension dist files and start passing the three env variables via secret. On my side I'll make sure the variables are configured on the repository before you merge it.
• Add a mention to the .env file on the README file explaining why and for what's is being used, and how to set it up when running the extension locally.

Thank you.

Done!

[crocodile-bounty-hunter]

solve comments from @ricardofelgueiras