Add newly introduced modifiers to our csharp_preferred_modifier_order editorconfig

[jkoritzinsky]

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

Author:	jkoritzinsky
Assignees:	-
Labels:	area-Infrastructure
Milestone:	-

[ghost]

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

Author:	jkoritzinsky
Assignees:	jkoritzinsky
Labels:	area-Meta
Milestone:	-

[jkoritzinsky]

Updated from main as there may have been usages of the current ordering rules that have crept in (such as the usages where I found this case) that I would need to fix before merging.

[jkoritzinsky]

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

Author:	jkoritzinsky
Assignees:	-
Labels:	area-Infrastructure
Milestone:	-

[ghost]

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

Author:	jkoritzinsky
Assignees:	jkoritzinsky
Labels:	area-Meta
Milestone:	-

[jkoritzinsky]

Updated from main as there may have been usages of the current ordering rules that have crept in (such as the usages where I found this case) that I would need to fix before merging.

[jkoritzinsky]

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

Author:	jkoritzinsky
Assignees:	-
Labels:	area-Infrastructure
Milestone:	-

[ghost]

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

Author:	jkoritzinsky
Assignees:	jkoritzinsky
Labels:	area-Meta
Milestone:	-

[jkoritzinsky]

Updated from main as there may have been usages of the current ordering rules that have crept in (such as the usages where I found this case) that I would need to fix before merging.

[jkoritzinsky]

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

Author:	jkoritzinsky
Assignees:	-
Labels:	area-Infrastructure
Milestone:	-

[ghost]

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

Author:	jkoritzinsky
Assignees:	jkoritzinsky
Labels:	area-Meta
Milestone:	-

[jkoritzinsky]

Updated from main as there may have been usages of the current ordering rules that have crept in (such as the usages where I found this case) that I would need to fix before merging.

[jkoritzinsky]

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

Author:	jkoritzinsky
Assignees:	-
Labels:	area-Infrastructure
Milestone:	-

[ghost]

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

Author:	jkoritzinsky
Assignees:	jkoritzinsky
Labels:	area-Meta
Milestone:	-

[jkoritzinsky]

Updated from main as there may have been usages of the current ordering rules that have crept in (such as the usages where I found this case) that I would need to fix before merging.

[jkoritzinsky]

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

Author:	jkoritzinsky
Assignees:	-
Labels:	area-Infrastructure
Milestone:	-

[ghost]

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

Author:	jkoritzinsky
Assignees:	jkoritzinsky
Labels:	area-Meta
Milestone:	-

[jkoritzinsky]

Updated from main as there may have been usages of the current ordering rules that have crept in (such as the usages where I found this case) that I would need to fix before merging.

[jkoritzinsky]

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

Author:	jkoritzinsky
Assignees:	-
Labels:	area-Infrastructure
Milestone:	-

[ghost]

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

Author:	jkoritzinsky
Assignees:	jkoritzinsky
Labels:	area-Meta
Milestone:	-

[jkoritzinsky]

Updated from main as there may have been usages of the current ordering rules that have crept in (such as the usages where I found this case) that I would need to fix before merging.

[jkoritzinsky]

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

Author:	jkoritzinsky
Assignees:	-
Labels:	area-Infrastructure
Milestone:	-

[ghost]

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The C# code style rule that reads this setting puts any unknown identifiers at the end of the list, which can cause confusing behavior (for example file coming after other modifiers like static instead of being at the start with the access modifiers). Update our value to add the modifiers introduced since we last wrote this.

Author:	jkoritzinsky
Assignees:	jkoritzinsky
Labels:	area-Meta
Milestone:	-

[jkoritzinsky]

Updated from main as there may have been usages of the current ordering rules that have crept in (such as the usages where I found this case) that I would need to fix before merging.