Gameplay Cue Notify Paths in Game Feature Modules don’t work when written in the ini file, only when added via AddGameplayCueNotifyPath()

The gameplay cue may work fine the first time. If this is the case, then relaunch the
editor. It should then be broken, as the tag is no longer loaded after its creation.

● Create a new 5.3 project
● Create a game feature module
● Add one or more gameplay tags in the new game feature module
● Create a gameplay cue with the new gameplay tag to trigger it, and create a gameplay effect to apply the cue
● Add a line to the ini file like the following: +GameplayCueNotifyPaths="/GameFeatureModule"
● Note how the above line does not cause the gameplay tag to be loaded
● Instead, use the following logic at an appropriate place to load the tag: UAbilitySystemGlobals::Get().GetGameplayCueManager()->AddGameplayCueNotifyPath(TEXT("/GameFeatureModule"));
● Note how this does work, which seems like inconsistent behavior