Investigate settings expand/collapse jank with avatar

On settings pages we have a general setting section. This contains an avatar component.

When this component's <img> is within the expandable content, there is consistent jank. The section will always expand as smoothly as it can (poor thing) up until the avatar component. After that the rest of the content below the img is rendered in a completely different pipeline, fresh and full reflow.

The general perf bottlenecks would mostly relate to single compositor layer and cpu calculating box props within that. We could definitely use a different method for these sections harnessing transform and could see a solid 60fps and can probably use gpu where available for the translation of the static content rather than full reflows.

In reality current implementation isnt too bad. It works and it works fine. I only tested on devices with decent cpu but I think its OK. I would first suggest we investigate if there is some rogue property relating to the img that is a known caveat.

I would regard this low priority, just here to track if we ever want to burn perf issues.