feat(cli): Add feast projects delete command (closes #5095)

[mailtoboggavarapu-coder]

Summary

Closes #5095

Exposes project deletion through the CLI by adding a new feast projects delete <name> subcommand to the existing projects group.

What's changed

Added project_delete command to sdk/python/feast/cli/projects.py:

Usage: feast projects delete [OPTIONS] NAME

  Delete a project and all its resources from the registry.

Options:
  -y, --yes  Skip confirmation prompt and delete immediately.
  --help     Show this message and exit.

Design notes

• Uses store.registry.delete_project(name, commit=True) via the lazy-init registry property (the abstract method exists in BaseRegistry and is implemented in all concrete registries)
• Adds an interactive confirmation prompt with click.confirm — can be skipped with --yes / -y for scripting
• Catches both FeastObjectNotFoundException and ProjectNotFoundException so the CLI exits cleanly (exit code 1) for either variant raised by concrete registry implementations
• Follows existing CLI patterns in projects.py

Example

# Interactive (prompts for confirmation)
feast projects delete my-project

# Non-interactive
feast projects delete my-project --yes

Checklist

• Added delete command to projects_cmd group
• Confirmation prompt with --yes bypass flag
• Error handling for non-existent projects
• Follows existing CLI patterns in projects.py

---

[mailtoboggavarapu-coder]

Thanks for the detailed review, @devin-ai-integration! Fixed both issues in commit 21f7f6a:

1. project_list — utils.py_object_to_proto + broken tag parsing: Updated to match master exactly: uses utils.tags_list_to_dict(tags) for tag filtering and prints tabulated output via tabulate.
2. project_current — simplified incorrectly: Fixed to match master (calls store.get_project(name=None) with try/except and YAML-formatted output).

The only new code is the project_delete command itself.

[mailtoboggavarapu-coder]

Hi team! Friendly ping on this PR — all 18 CI checks are passing and there are no conflicts with the base branch.

This adds a feast projects delete command (closes #5095) with an interactive confirmation prompt and a --yes / -y flag for scripting. Happy to iterate on any feedback!

[mailtoboggavarapu-coder]

Hi team! 👋 Friendly ping on feast #6318 — this adds feast projects delete <name> to the CLI (closes #5095).

Status as of today:

• ✅ DCO passing
• ✅ Devin Review completed
• ✅ Branch synced with master
• ⏳ 11 workflows awaiting maintainer CI approval (fork policy)

The only blocker is maintainer CI approval + code review. Happy to address any feedback!

[ntkathole]

@mailtoboggavarapu-coder I think it's better to include delete_project method in sdk/python/feast/feature_store.py

See #6212

Let's add it to feature_store.py and remove context passing in cli

[mailtoboggavarapu-coder]

Hi @ntkathole 👋 — all unit tests, smoke tests, and most integration tests are now passing after the indentation fix. Two checks are failing but neither is caused by this PR's changes:

1. linter — detect-secrets is flagging infra/feast-operator/bundle/manifests/openlineage-secret_v1_secret.yaml, a file this PR does not touch (pre-existing repo issue).

2. pr-integration-tests — exited with code 2 (pytest "interrupted") after 16+ minutes, indicating a cloud infrastructure/timeout flake rather than a test assertion failure. All other integration test workflows (DuckDB, Ray, remote-rbac, registry REST API, local) passed.

Could you please re-run the pr-integration-tests job? It appears to be a transient infrastructure failure unrelated to this change. Thank you! 🙏