This matches the corresponding existing case in AArch64LoadStoreOpt::findMatchingUpdateInsnForward.
Both cases could also be modified to check MBBI->getFlag(FrameSetup/FrameDestroy) instead of forbidding any optimization involving SP, but the effect is probably pretty much the same.
If we're using the same code to do this check in multiple places, should we factor it out?