Only Rerender "DAO Connected" Components

Only rerender components that are "DAO Connected".

This can be done through supporting a subscription model, where components that depend on additional contextual information (ex: , ).

For example, consider...
```html

{data => (

)}

```
Ideally, if Arc.Config's web3 provider changes, View1 & 2 shouldn't have to rerender, but View3 should because the data may be different. This can be partially achieved if DAO connect's the Arc.Config's subscriber list, which will cause it to be told to rerender if the config ever changes, but this only causes View1 to not be rendered. View2 would still be rendered because currently the data is stored within the Component's state (the DAO's state), which would cause View2 to still be rendered.

Going to leave this here for now, as it'll be interesting to come back to this after some metrics have been gathered, as I feel this may be premature optimization.

Beginne mit der Überprüfung des für Arc.Config, DAO und DAO.Data beschriebenen Verhaltens der Komponentenabonnements, insbesondere wie Zustandsaktualisierungen von DAO erneute Renderings auslösen. Erfasse die vorgeschlagenen Metriken, bevor du entscheidest, ob die Optimierung weiterverfolgt werden soll; als erledigt gilt die Festlegung eines gemessenen, abgestimmten Umfangs für erneute Renderings ausschließlich von mit DAO verbundenen Komponenten.

Vom Indexierungsmodell aus dem Issue-Text verfasst.