Update project description

[daviddavis]

📜 Checklist

• Commits are cleanly separated with meaningful messages (simple features and bug fixes should be squashed to one commit)
• A changelog entry or entries has been added for any significant changes
• Follows the Pulp policy on AI Usage
• (For new features) - User documentation and test coverage has been added

See: Pull Request Walkthrough

[Copilot]

Pull request overview

Updates the package metadata in pyproject.toml to better reflect the plugin’s purpose within the Pulp ecosystem.

Changes:

• Refines the description field to describe scheduling/orchestrating workflows of tasks.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[patchback]

Backport to 0.2: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 75b6f79 on top of patchback/backports/0.2/75b6f7987d36852192199b4b9b39245667210525/pr-42

Backporting merged PR #42 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/pulp/pulp_workflow.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/0.2/75b6f7987d36852192199b4b9b39245667210525/pr-42 upstream/0.2

4. Now, cherry-pick PR Update project description #42 contents into that branch:

   $ git cherry-pick -x 75b6f7987d36852192199b4b9b39245667210525

   If it'll yell at you with something like fatal: Commit 75b6f7987d36852192199b4b9b39245667210525 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 75b6f7987d36852192199b4b9b39245667210525

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Update project description #42 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/0.2/75b6f7987d36852192199b4b9b39245667210525/pr-42

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.