Use ASSIGNCOPY for NSAccessibilityElement string setters

[Copilot]

Addresses feedback from PR #362 to use ASSIGNCOPY instead of ASSIGN for string attribute setters in NSAccessibilityElement.m to prevent issues with mutable strings being modified after assignment.

Changes

• String setters: Updated setAccessibilityLabel:, setAccessibilityIdentifier:, setAccessibilityRole:, and setAccessibilitySubrole: to use ASSIGNCOPY
• Initializer: Updated initWithRole:frame:label:parent: to use ASSIGNCOPY for role and label parameters

// Before
- (void) setAccessibilityLabel: (NSString *)label
{
  ASSIGN(_accessibilityLabel, label);  // retains
}

// After
- (void) setAccessibilityLabel: (NSString *)label
{
  ASSIGNCOPY(_accessibilityLabel, label);  // copies
}

This prevents potential bugs where a caller passes an NSMutableString, then mutates it after assignment.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[rmottola]

Does this make sens at all at a first glance? parameters are NSStrings and not mutable, aren't they? is there a deeper issue?

[fredkiefer]

As the AI already explained, the parameter could as well be an NSMutableString, which is a sub class of NSString (Actually it is more complicated, as NSString is a class cluster, but we will ignore that for now).
The good thing here is, that for NSString copying is a very cheap operation, it will just return the object itself.

[gcasa]

This PR is outdated since I moved these into another class.