fix: use constants in ConfigManager

[Arcitec]

Spotted this issue while looking at some recent changes.

Fixes ConfigManager to always use the defined constants, so that it won't break if the constant values are changed in the future.

I also ripgrep'd the rest of the codebase and did not come up with any other locations where the strings are used instead of the constants, so it seems fine now.

---

I was unsure about this location though:

comfy-cli/comfy_cli/workspace_manager.py

Lines 135 to 139 in 6be00e4

	class WorkspaceType(Enum):
	CURRENT_DIR = "current_dir"
	DEFAULT = "default"
	SPECIFIED = "specified"
	RECENT = "recent"

It doesn't seem like it should be using CONTEXT_KEY_RECENT = "recent" instead of hardcoding. Perhaps someone can confirm that the workspace manager keys are indeed totally separate from the config keys.

[codecov]

Codecov Report

❌ Patch coverage is 20.00000% with 4 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
comfy_cli/config_manager.py	20.00%	4 Missing ⚠️

@@           Coverage Diff           @@
##             main     #299   +/-   ##
=======================================
  Coverage   47.96%   47.96%           
=======================================
  Files          30       30           
  Lines        3077     3077           
=======================================
  Hits         1476     1476           
  Misses       1601     1601           

Files with missing lines	Coverage Δ
comfy_cli/config_manager.py	50.00% <20.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[bigcat88]

Perhaps someone can confirm that the workspace manager keys are indeed totally separate from the config keys.

I guess WorkspaceType is related only to path of workspace.

It was added by this commit

so no need to replace recent there with CONTEXT_KEY_RECENT (at least for now)

---

Regarding this PR - I think we can replace the values with constants, logically everything seems fine.

[Arcitec]

@bigcat88 Ah yeah from the commit you linked, it seems like the WorkspaceType enum is just a marker to tell the caller "what type of workspace path was returned", so that part shouldn't be changed. Good good. :) 👍