Clarify in the Binding Overview what binding are and when to use them.

Below is an example thread where people wonder what binding are, especially then some of them overlap with other components like state. Current we just say what they do, not when and how to think about this.
This is to update the overview section of the https://docs.dapr.io/developing-applications/building-blocks/bindings/bindings-overview/ topic.

Lenny — Today at 4:17 AM
Hi! I have a bit of a seemingly stupid question to which I have a partial answer but can anybody explain the concrete difference between the State store and binding component for Azure Storage Accounts?

Oli — Today at 6:05 AM
State Stores are a vendor agnostic abstraction around storing state, particularly Key Value state. Portability between the various state stores components is a big part of its value proposition.

On the other hand....

Bindings are a specialism. Nothing to do with creating an agnostic abstraction across vendors and technologies. Bindings will often have behaviours and capabilities that don't fit into the vendor agnostic abstraction of State Stores.

berndverst (maintainer) — Today at 11:48 AM

@Lenny yes the difference is.. for the Azure Blob Storage Binding we added all the things to the binding that people wanted but that aren't part of the standard state store interface. State stores only support a very specific set of capabilities. But Binding is a free for all.. no two bindings can be used interchangeably.