You have to use the standard signal names to define signal roles in an interface for a custom component. A SystemVerilog interface is not exactly the same as a Platform Designer interface. In the example, it shows 4 signals: address, write, writedata, and readdata. These match the names that must be used for Avalon. You can use different names in your code but then there must be a mapping to the correct signal roles for the Platform Designer interface using SV_INTERFACE_SIGNAL to add the signals to the interface and SV_INTERFACE_SIGNAL_NAME to do the name mapping: https://www.intel.com/content/www/us/en/docs/programmable/683609/23-3/port-properties-38884.html. With a SV interface, you can use the USE_ALL_PORTS property, but then the signal names in your SV interface must exactly match the signal roles defined in the spec: https://www.intel.com/content/www/us/en/docs/programmable/683091/22-3/memory-mapped-interface-signal-roles.html
So the short and easiest answer is if your signal names in your SV interface match the required signal role names in the Avalon spec, you can just use USE_ALL_PORTS to set up the interface.