Fix refresh strategy for the history

[teolemon]

The refresh strategy for the history is confusing. Beyond the recent schema change, products get completed on a rolling basis.
To 'fix" products in my history, I have to:

• Open the product
• Open the menu to refresh
• See the Eco-Score appear on the summary card
• Move to the next product.

I would expect a more agressive refresh strategy (attempt to refresh silently on product opening, and refresh on "pull to refresh" in history

Originally posted by @teolemon in #788 (comment)

[monsieurtanuki]

@teolemon We don't have the same problem for the search list, because the local database is queried ("same search already?") and its products are displayed, with a snackbar mentioning the possibility of a refresh (list + product data).

In a first approach, I can add a "refresh" button and method to the history page, that would refresh the products of the history - not the history itself of course. The choice of the most relevant UI/UX for that will come next.

Regarding the product page, the method _refreshProduct is already there in new_product_page.dart, and is triggered by a "refresh" menu item.

[monsieurtanuki]

From #1192, just one click from history page updates the history products.

As @M123-dev pointed out, the coded solution will not be good if we have 1000s of products in the history, but neither will the whole app, as one of the 3 preloaded tabs displays the history page that first loads ALL the history products and then displays them in a more elegant way with ListView.builder.

Does it make sense to keep 1000s of products in history? Should we display them page by page? Should we truncate the history to a reasonable (?) size?

If those questions are interesting enough for the project (given its goals), please feel free to create a specific issue or discussion.

Now I close this issue, as it's now possible very easily to refresh the history. @teolemon If you prefer a more automatic process, please create a new issue.