Publish Retired Knowledge articles again

[Soumyadeep10]

PR Description:

Please Note: Before you move on with this PR, I would like to let you know that some commits from yesterday and before that have automatically been included inside this PR. These are already accepted and merged so please ignore them. There are only 2 new commits from today.

UI Action:
Publish a Retired Knowledge Article again after it is already retired.

How it works:

1. The code finds existing articles in the Knowledge base that share the same Article ID but are not the current article and are 'retired'.
2. It updates the workflow state of these found articles to 'outdated'.
3. For the current article, it sets the workflow_state to 'pubblished', records the current date and updates the 'published' field with the date.
4. It also removes the pre-existing 'retired' date from the 'retired' field.
5. It redirects the user to the updated current record.

Pull Request Checklist

Overview

• Put an x inside of the square brackets to check each item.
• I have read and understood the CONTRIBUTING.md guidelines
• My pull request has a descriptive title that accurately reflects the changes and the description has been filled in above.
• I've included only files relevant to the changes described in the PR title and description
• I've created a new branch in my forked repository for this contribution

Code Quality

• My code is relevant to ServiceNow developers
• My code snippets expand meaningfully on official ServiceNow documentation (if applicable)
• I've disclosed use of ES2021 features (if applicable)
• I've tested my code snippets in a ServiceNow environment (where possible)

Repository Structure Compliance

• I've placed my code snippet(s) in one of the required top-level categories:
  • Core ServiceNow APIs/
  • Server-Side Components/
  • Client-Side Components/
  • Modern Development/
  • Integration/
  • Specialized Areas/
• I've used appropriate sub-categories within the top-level categories
• Each code snippet has its own folder with a descriptive name

Documentation

• I've included a README.md file for each code snippet
• The README.md includes:
  • Description of the code snippet functionality
  • Usage instructions or examples
  • Any prerequisites or dependencies
  • (Optional) Screenshots or diagrams if helpful

Restrictions

• My PR does not include XML exports of ServiceNow records
• My PR does not contain sensitive information (passwords, API keys, tokens)
• My PR does not include changes that fall outside the described scope

[bird-03]

Hi @Soumyadeep10

Thank you for your participation and contribution!

Looks good, this will be nice script to re-publish a retired Knowledge Base (KB) article while marking any previous retired versions of the same article as outdated.

Keep contributing and Happy Hacking

[Soumyadeep10]

Thank you @bird-03 !!