deprecation warnings from pyvo incorrectly indicate an Astropy issue

The deprecated [decorator](https://github.com/astropy/pyvo/blob/e60ace98fcdb88f141ea3e9c22b4722e23e18031/pyvo/dal/vosi.py#L9) which is imported from astropy produces warnings that indicate that the deprecation comes from Astropy instead of pyvo.

Could the deprecation warnings be reworked so that they correctly indicate that the deprecation is in pyvo instead of astropy?

Perhaps the decorator could still be reused from astropy but adapted for pyvo. it [looks like](https://github.com/astropy/astropy/blob/7f259327a77787abe7caa1ac5b7103f39a7c4389/astropy/utils/decorators.py#L32) if you pass warning_type or pending_warning_type with custom pyvo classes it might resolve this issue.

Start with pyvo/dal/vosi.py and compare the imported decorator with astropy/utils/decorators.py, especially its warning_type and pending_warning_type handling. Trace how the deprecation warning is produced and confirm that the resulting warnings identify pyvo rather than Astropy; no test file is named in the issue.

Written by the indexing model from the issue text.