Allow custom fields with same name in Automation using custom field ID

Currently, if custom fields with the same name but a different type exists, the "Field value changed" trigger doesn't show both fields while configuring the automation rule.

Steps to Reproduce:

1. Create custom fields with the same names but a different type as below:
   
2. Configure automation rule with "Field value changed" trigger, it only shows one field.

Additionally, it would be great if there is an internal alias on the custom fields that could be used/displayed on the configuration page.

Workaround:
Rename one of the custom field names to use in automation rules.