CHANGES(docs[deprecations]): Add Deprecated and Raises version columns

why: Users need to know both when deprecation started and when methods
will raise DeprecatedError to plan their migration timeline.
what:
- Add "Deprecated" column showing original deprecation version
- Add "Raises" column showing v0.51.0 for all deprecated APIs
- Update all rows with appropriate version numbers
- Use Sphinx autodoc links for DeprecatedError and DeprecationWarning

Author: tony

CHANGES

@@ -46,7 +46,7 @@ _Upcoming changes will be written here._
 
 #### APIs deprecated (#611)
 
-Legacy API methods now raise `libtmux.exc.DeprecatedError` (hard error) instead of emitting `DeprecationWarning`.
+Legacy API methods now raise {exc}`~libtmux.exc.DeprecatedError` (hard error) instead of emitting {class}`DeprecationWarning`.
 
 See {doc}`migration` for full context and examples.