Commonly used blueprint conversion functions should be promoted to top level category

Many useful blueprint utility nodes are buried in the Utility category and are not very discoverable by users. This leads to them choosing other nodes that are much less convenient and efficient. This can be fixed per node by promoting to the "|" category if we highly suspect it's what the user want, like in UK2Node_BreakStruct::GetMenuActions. There are two case that come to mind, but there may be others:

For Structs, break struct is promoted to the top level, but Set Members is not. This often leads to users doing a break struct of something massive like post process settings, changing one member, and then making with tons of individual links. If we showed them Set Member they would probably use that much more efficient method instead

For Soft References, the Resolve node that converts into a hard reference is named somewhat obscurely and is a collapsed node so many users will not know what it is called. If we promoted it, they would try it at least one and learn the connection

1. Add Struct and Soft Reference to Object variables to a blueprint
2. Place a get node for each function
3. Drag off of the struct and note that Break is promoted to the default category, but the just as useful Set Member function is hidden deep in utilities
4. Drag off of the soft reference and note that Resolve is hidden deep in utilities