feat: ComponentKey API

[erickzanardo]

Description

This PR adds a new key api on FCS, which will allow users to get a component from the tree, without needing to iterate over all the children or a parent descendants.

Checklist

• I have followed the Contributor Guide when preparing my PR.
• I have updated/added tests for ALL new/updated/fixed functionality.
• I have updated/added relevant documentation in docs and added dartdoc comments with ///.
• I have updated/added relevant examples in examples or docs.

Breaking Change?

• Yes, this PR is a breaking change.
• No, this PR is not a breaking change.

Related Issues

[spydon]

Lgtm, maybe just add a specific example for the keys?

[erickzanardo]

Lgtm, maybe just add a specific example for the keys?

I considered that, but I felt that this example wouldn't show anything much visual, so I went with changing an existent example to make use of the new API.

Do you feel we needed to have a dedicated example only for the key api? and if so, any idea how that example would look like?

[spydon]

I considered that, but I felt that this example wouldn't show anything much visual, so I went with changing an existent example to make use of the new API.

Do you feel we needed to have a dedicated example only for the key api? and if so, any idea how that example would look like?

It would be hard for a user to find out that the key api example is on the keyboard example.
A little bit hard to visualize the feature, but maybe one could show the components key id on top of some simple components and click on some buttons that are on some other place on the screen that looks up the component in the tree and adds some simple effect on it?

[erickzanardo]

@spydon added a more specific example, let me know what you think

Screen.Recording.2023-06-20.at.08.57.00.mov

[spydon]

@spydon added a more specific example, let me know what you think

Screen.Recording.2023-06-20.at.08.57.00.mov

Cute! Love it, and it should be clear what is happening too 😊