This allows the -fstack-clash-protection option to be used for AArch64
Linux.
Linux for AArch64 uses a 64k stack guard, instead of the 4k guard
assumed by the backend, so we set the stack-probe-size function
attribute to configure this, and the -mstack-probe-size= option can be
used to override this.
Would it be worth always setting the stack-probe-size attribute so that it is always correct and to avoid the risk of it going out-of-sync in case of changes to the assumed size in the backend?