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.

Commencez par examiner le comportement des abonnements de composants décrit pour Arc.Config, DAO et DAO.Data, en particulier la manière dont les mises à jour de l’état de DAO déclenchent de nouveaux rendus. Recueillez les métriques proposées avant de décider s’il faut poursuivre l’optimisation ; le travail est considéré comme terminé lorsqu’un périmètre mesuré et convenu a été défini pour ne relancer le rendu que des composants connectés à DAO.

Rédigé par le modèle d'indexation à partir du texte de l'issue.