Renaming/changing arity of a reloadable type is not handled correctly #54881
Description
The general problem is that we use symbol keys to resolve symbols between old and new compilation on some code paths in the semantic analysis.
A type that is renamed or whose arity is changed does not resolve anymore. This is not a problem for regular types since their rename/arity change is a rude edit, but for reloadable types these operations should be allowed and result in a new type.
The solution would be to process symbol renames first and then apply the mapping to the symbol key resolution so that the resolution can find the symbol using its previous name.
Related: #54886
See skipped tests.