Mark TarOutputStream as restricted

[StefanSpieker]

I'm pretty sure that it is not used anymore, because the search just shows no usage at all:
https://github.com/search?q=org%3Ajenkinsci+TarOutputStream&type=Code

Proposed changelog entries

• Internal: Removed deprecated TarOutputStream

Submitter checklist

[oleg-nenashev]

It is being used in of CloudBees proprietary plugins. CC @jtnord @amuniz .
Unfortunately, just searching GitHub is not always enough, because there are hundreds(thousands?) of private-source plugins created by Jenkins user companies and vendors

[daniel-beck]

Also, unfortunately we still distribute some plugins outside the jenkinsci org from several years ago.

For those, https://github.com/jenkins-infra/deprecated-usage-in-plugins works better as it downloads all currently distributed plugins and searches for uses of classes from a list of names.

[oleg-nenashev]

Putting @Restricted(DoNotUse.class) could be a good option once jenkinsci/lib-access-modifier#17 is released. @Restricted(NoExternalUse.class) can be used as a workaround to highlight deprecation for plugin maintainers. PCT will not fail, so why not?

[StefanSpieker]

Ok, that is a good idea. I also added this annotation to the TarInputStream and already created PRs for plugins which still use this class:
jenkinsci/copy-to-slave-plugin#11
jenkinsci/fstrigger-plugin#4

[daniel-beck]

Probably the most pragmatic approach.

@RestrictedSince might be helpful too.

[oleg-nenashev]

+1 for @RestrictedSince. We can safely assume it lands in the next weekly (2.200)

[StefanSpieker]

I added the @RestrictedSince("2.200") as suggested

[oleg-nenashev]

Thanks!

[oleg-nenashev]

I plan to merge it tomorrow if no negative feedback