[FormControlRange] Add naming of setFormControlRange() to Open Questions (#1165)

The redundant naming of setFormControlRange() came up during [spec discussions](https://github.com/whatwg/dom/pull/1404/files#r2380522739), so adding the question to the Explainer.

Author: stephanieyzhang

FormControlRange/explainer.md

@@ -581,7 +581,7 @@ It has been [discussed](https://github.com/whatwg/html/issues/11478#issuecomment
 Such use cases might also prompt revisiting the current `FormControlRange` name in favor of something broader, such as `ElementRange`, to better reflect its applicability beyond form controls.
 
 ## Open Questions
-How should `FormControlRange` behave when callers provide reversed offsets (i.e. `startOffset > endOffset`)? 
+#### How should `FormControlRange` behave when callers provide reversed offsets (i.e. `startOffset > endOffset`)? 
 
 Consider the following ideas:
 - Throw `IndexSizeError`.
@@ -607,6 +607,8 @@ range.setFormControlRange(input, 4, 0);
 
 Note: With reversed endpoints, DOM `Range` setters collapse them to a single point, whereas `Selection` preserves directionality (anchor/focus). Collapsing is the current interoperable behavior, but alternatives remain open for discussion.
 
+#### Is `setFormControlRange()` redundant with the type name? Would `setRange`, `set`, `setStartAndEnd`, or something else better align with `Range`/`StaticRange` naming? 
+
 ## References & acknowledgements
 
 Many thanks for valuable feedback and advice from: