DEPR: Deprecate use of un-supported numpy dt64/td64 dtype for pandas.array
- [X] closes #53058
- [x] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [x] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [x] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [X] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

@jbrockmendel Would you be able to take a look at this PR and let me know if its good to go? Oh, i see.  #53058 isnt about deprecating all dt64/td64 dtypes, just the unsupported units.  we support s, ms, us, ns. In pd.array, at the end where we have checks for is_supported_dtype, do an 'else' statement and issue a deprecation warning @jbrockmendel I should add a deprecation warning rather than a TypeError? I was thinking that we wanted to [raise an error](https://github.com/pandas-dev/pandas/issues/53058#issuecomment-1566289538) rather than a deprecation warning?

Is the image below what you're looking for? If we use an else statement I think that we'll be throwing a deprecation warning for other supported dtypes before we hit the return statement at the bottom.

 I had my td64/dt64 check up top. Are we okay with me adding an elif statement at the bottom and checking for the unsupported types?

![image](https://github.com/pandas-dev/pandas/assets/45905457/3ce1b9b3-6794-499d-819a-ff4f77c74e68)
 @jbrockmendel PR is ready for inspection. Failing test does not appear to be related to PR @jbrockmendel PR is ready for inspection @jbrockmendel Fixed PR based on recommendations and pinging on green! @jbrockmendel PR is ready for inspection. 

Failing tests are unrelated to PR. Doctest and code checks are passing