BUG: Fix DataFrame constructor misclassification of array-like with 'name' attribute (#61443)

[iabhi4]

BUG: Fix DataFrame constructor misclassification of array-like with 'name' attribute

Previously, any object with a .name attribute (like some vtkArray-like objects) was assumed to be a Series or Index, causing the DataFrame constructor to misinterpret the input and raise errors when passed valid 2D array-likes.

This fix ensures we only apply the named-Series/Index logic when the input is actually an instance of ABCSeries or ABCIndex, and the name is not None.

A new test was added to ensure array-like subclasses with .name are handled correctly.

---

• Closes BUG: DataFrame constructor not compatible with array-like classes that have a 'name' attribute #61443
• Tests added and passing
• Code passes all checks via pre-commit
• Behavior verified with array-like + .name case

[iabhi4]

Note: One unrelated pre-commit check failed:

Check for strings with misplaced spaces.................................................................Failed
- hook id: unwanted-patterns-strings-with-misplaced-whitespace

pandas/_libs/tslibs/offsets.pyx:5112: String has a space at the beginning instead of the end of the previous string.
pandas/_libs/tslibs/offsets.pyx:5126: String has a space at the beginning instead of the end of the previous string.

One of the flagged lines includes:

f" instead.",

This has a space at the start of the string rather than the end of the previous one, which violates the unwanted-patterns-strings-with-misplaced-whitespace pre-commit rule.

Since this file wasn't touched in this PR and is unrelated to the fix, I’ve left it as-is. Let me know if you'd like me to patch it.