Select Fields which appear in KiCad

[foreverimagining]

Is your feature request related to a problem? Please describe.
I found this project just a couple days ago because I was hoping for a way to store information about components that I select and/or have in stock that would be easily imported into KiCad so I don't have to manually input data for each part every time I make a new project or copy-and-paste from one project to another. It does a great job at that, and KiCad 8 is fantastic as well. However, since I plan to share some of my projects as open-source hardware, I want to make it easy for people to identify the specific components I use at common distributors by including their particular part numbers. Unfortunately, only a few fields are actually included in the information passed to KiCad, and I don't consider the manufacturer's part number to be quite sufficient when it can sometimes turn up alternatives in searches.

Describe the solution you'd like
I would like to be able to select which fields are exposed to KiCad besides the standards that are already included. This should include selecting parameters as well as distributor information. I mostly want to be able to add distributor part numbers which should have field names associating them with the distributor, but I can foresee cases where I might want to include important parameters that might have an impact on component selection in the projects. For implementation in the UI, perhaps a checkmark field next to each parameter and distributor information would be the simplest way to toggle inclusion? If this is included on the pricing information, we could even include the price for the distributor we would be buying from (likely the lowest cost option that fulfills the number of pieces needed).

Describe alternatives you've considered
Unless/until this feature is added, I figure I will just have to input the distributor part numbers manually. It won't be completely awful if I wait until the end of the project when all of the components are decided and then use the bulk-edit feature in conjunction with Part-DB as a reference. It's still a time-saver as-is.

Thank you so much for all the work you've done on this. It really solves a problem for me, and I look forward to seeing if I can integrate this into my Grocy and/or Home Assistant instances using the API for automation when I have more time in the future.