Renaming a BP interface function/event breaks all existing uses of that function/event

If you rename a blueprint interface function or event that is used somewhere in a blueprint, it will break the usage of that function/event. If it was a function, it will actually delete all the BP logic you had set up inside the interface function to create the return value(s). If it was an event, the event does not get renamed correctly.

Found in 4.19 CL# 4033788. Reproduced in 4.18 CL# 3832480 and 4.20 Main CL# 4088075

1. Open the editor
2. Create a new blueprint interface
3. In the interface add a function called "OldEvent" and add a boolean input
4. In the interface add another function called "OldFunction" and add both a boolean input and output
5. Compile and save your interface
6. Create an actor blueprint
7. In the class settings implement your interface
8. In the event graph of your actor add a "Event OldEvent" and hookup a print string
9. In the interface panel of the actor blueprint add a print string and a boolean variable as a return value
10. Compile and Save
11. Open your interface blueprint and rename both functions to "NewEvent" and "NewFunction" respectively

Result:
The functions from the interface will no longer function and will be renamed incorrectly in the actor blueprint.

Expected:
Functions from the interface will work as intended and will be renamed properly in the actor blueprint.

Steps for project:

1. Open the attached project
2. Open "TestInterface" and rename both functions to "NewEvent" and "NewFunction" respectively
3. Compile and Save the interface
4. Open "TestBP"

Result:
The functions from the interface will no longer function and will be renamed incorrectly in the actor blueprint.