Deprecate humanitec plugins because hey have their own repo now

[taras]

Motivation

Humanitec folks are maintaining their plugins in https://github.com/humanitec/humanitec-backstage-plugins we can deprecate these now.

Approach

Added deprecate messages to each package in package.json

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8ebd58c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[frontsidejack]

The following preview packages were published:

Name	Version	Install Command
@frontside/backstage-plugin-humanitec-common	0.3.14-tm-deprecate-humanitec-plugins.0	yarn add @frontside/backstage-plugin-humanitec-common@tm-deprecate-humanitec-plugins
@frontside/backstage-plugin-humanitec	0.3.16-tm-deprecate-humanitec-plugins.0	yarn add @frontside/backstage-plugin-humanitec@tm-deprecate-humanitec-plugins
@frontside/backstage-plugin-humanitec-backend	0.3.18-tm-deprecate-humanitec-plugins.0	yarn add @frontside/backstage-plugin-humanitec-backend@tm-deprecate-humanitec-plugins

Generated by @thefrontside/actions

[johanneswuerbach]

I don’t see this field in https://docs.npmjs.com/cli/v10/configuring-npm/package-json , could you point me to some documentation around this?

package.json | npm Docs

Specifics of npm's package.json handling

[taras]

It's part of our publish actions. The action will automatically call npm deprecate when it encounters this this property in package.json