refactor(module: select): use Func to get or set value instead of reflection

[Zonciu]

🤔 This is a ...

• New feature
• Bug fix
• Site / documentation update
• Demo update
• Component style update
• Bundle size optimization
• Performance optimization
• Refactoring
• Code style optimization
• Test Case
• Branch merge
• Other (about what?)

🔗 Related issue link

💡 Background and solution

📝 Changelog

Language	Changelog
🇺🇸 English	use Func to get/set value instead of reflection
🇨🇳 Chinese	使用Func代替反射读写数据

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• Changelog is provided or not needed

[anddrzejb]

@Zonciu I am not a reflection and expression tree expert, so correct me if I am wrong. My understanding after having a very brief look at your code, is that you are still using reflection, but instead of every time, you basically "compile" it on set and when it is used, it is just using compiled code instead of going through reflection again. This is where your performance boost is coming from. So we may loose a bit more time during first rendering, but gain time on every item processing when value/label is required to be extracted to set.

[Zonciu]

@anddrzejb You are right, and we can make it go further if it is necessary: caching typeof(TItem) , typeof(TItemValue) , LabelName , DisabledName , GroupName as cache key to reuse those Expression delegates

[anddrzejb]

Sounds really cool. I have seen reflection quite often used in other components (for example DatePicker, a big performance offender), it would be really nice if we could somehow make the helper you made universal. But this is maybe for some other time. I do not have time unfortunately to checkout your code today and I am leaving for couple of days, so either @ElderJames can review it or I will once I came back after Sunday. Sorry... 😞

Maybe you could propose your caching idea here as well in the meantime?

[Zonciu]

I will create a Func cache commit for this.

Actually I have made a helper for property accessing, it works on table component, see Path-based property access