H-2722: Add AI-generated name for flow runs

[CiaranMn]

🌟 What is the purpose of this PR?

This PRs adds a way of distinguishing between runs of a given flow type by assigning a name to them.

The name is:

• fixed to [Auto-] Analyze URL: [url] in the case of browser-triggered flows
• generated by an LLM from the flow inputs in other cases

It uses this name in the frontend UI where flow runs are listed, as well as on the page for the flow run.

Since I was editing the Flow entity type I've taken the opportunity to rename it to Flow Run to distinguish it from Flow Definitions.

Pre-Merge Checklist 🚀

🚢 Has this modified a publishable library?

This PR:

• [x] does not modify any publishable blocks or libraries, or modifications do not need publishing

📜 Does this require a change to the docs?

The changes in this PR:

• [x] are internal and do not require a docs change

🕸️ Does this require a change to the Turbo Graph?

The changes in this PR:

• [x] do not affect the execution graph

🐾 Next steps

The quality of the outputted name will probably need improving based on further usage.

🛡 What tests cover this?

• None yet

❓ How to test this?

1. Start any flow, see what name it is given.

📹 Demo

Name generated from input

https://github.com/hashintel/hash/assets/37743469/096e1cde-e6eb-4999-be10-5e28002646e8

Fixed name for browser-base flows