Replace outdated factories info with sharing workspace with devfile URL

[sleshchenko]

Read our Contribution guide before submitting a PR.

What does this PR do?

This PR replaces outdated factories info with sharing workspace with devfile URL in the publishing plugin article.
Modified article https://5fda36a78a76bb0fd46c4038--eclipse-che-docs-pr.netlify.app/che-7/contributor-guide/publishing-che-theia-plug-ins/

What issues does this PR fix or reference?

It's done in the scope of eclipse-che/che#18518

Specify the version of the product this PR applies to.

7.23 and even earlier

PR Checklist

As the author of this Pull Request I made sure that:

• vale has been run successfully against the PR branch
• Link checker has been run successfully against the PR branch
• Documentation describes a scenario that is already covered by QE tests, otherwise an issue has been created and acknowledged by Che QE team
• Changed article references are updated where they are used (or a redirect has been set up on the docs side):
  • Dashboard branding.json
  • Chectl constants.ts

[sleshchenko]

This section is mostly copy/paste from removed factory section where I replaces removed persisted factories with che-host/f?url=... link.
For me, it does not seem detailed and clear enough but I don't have any experience with writing plugins and not sure how it can be made better.

[themr0c]

Suggested change

	Reference URL examples:
	+
	* pass:[https://custom-registry/v3/plugins/custom-plugin-name/0.0.1/]
	* pass:[https://raw.githubusercontent.com/username/che-custom-plugins/master/v3/plugins/custom-plugin-name/0.0.1/meta.yaml]
	.`chePlugin` reference URL pointing to a plug-in `meta.yaml`
	====
	----
	https://custom-registry/v3/plugins/custom-plugin-name/0.0.1/
	https://raw.githubusercontent.com/username/che-custom-plugins/master/v3/plugins/custom-plugin-name/0.0.1/meta.yaml
	----
	====

[sleshchenko]

It seems to be not URL but URLs, I'm not sure if we need provide them as separate examples or one with URLs in title

[sleshchenko]

I've applied:

.`chePlugin` reference URLs pointing to a plug-in `meta.yaml`
====
----
https://custom-registry/v3/plugins/custom-plugin-name/0.0.1/
https://raw.githubusercontent.com/username/che-custom-plugins/master/v3/plugins/custom-plugin-name/0.0.1/meta.yaml
----
====

But can split them to separate example, or just replace URLs -> URL if needed.

[themr0c]

Suggested change

	* {prod-url-secure}/f?url=https://github.com/eclipse/che
	* {prod-url-secure}/f?url=https://raw.githubusercontent.com/eclipse/che/master/devfile.yaml
	.`chePlugin` reference URL pointing to a repository containing a devfile
	====
	{prod-url}/f?url=https://github.com/eclipse/che
	====
	+
	.`chePlugin` reference URL pointing to a devfile
	====
	{prod-url}/f?url=https://raw.githubusercontent.com/eclipse/che/master/devfile.yaml
	====

[sleshchenko]

That's not chePlugin reference but a link to Che that will create a workspace via Factory flow with cheplugin inside after plugin author added it into devfile 💥

[sleshchenko]

I've applied

.Factory URL pointing to a repository containing a devfile
====
{prod-url}/f?url=https://github.com/eclipse/che
====
+
.Factory URL pointing to a devfile
====
{prod-url}/f?url=https://raw.githubusercontent.com/eclipse/che/master/devfile.yaml
====