itdove/devaiflow#372: docs: Replace instance-specific JIRA field IDs with generic placeholders

[itdove]

Jira Issue: https://redhat.atlassian.net/browse/itdove/devaiflow#372

Description

This PR replaces hardcoded, instance-specific JIRA field IDs with generic placeholders throughout the codebase and documentation. This change improves portability and maintainability by decoupling the code from specific JIRA instance configurations.

Changes include:

• Updated devflow/jira/client.py and devflow/jira/field_mapper.py to use generic field ID references
• Replaced instance-specific field IDs in documentation (docs/guides/troubleshooting.md)
• Updated test fixtures and assertions in tests/test_field_mapper.py, tests/test_jira_update_command.py, and tests/test_jira_update_command_functions.py to reflect generic placeholder patterns
• Updated DevAIFlow session artifacts in .wolf/ directory

This refactoring makes the codebase more adaptable to different JIRA instances without requiring code changes for instance-specific field mappings.

Assisted-by: Claude

Testing

Steps to test

1. Pull down the PR
2. Run the full test suite to verify all tests pass with the updated field ID references: pytest tests/
3. Verify that tests/test_field_mapper.py passes with generic placeholder assertions
4. Verify that tests/test_jira_update_command.py and tests/test_jira_update_command_functions.py pass with updated field ID patterns
5. Review the troubleshooting documentation to ensure field ID examples are clear and generic: docs/guides/troubleshooting.md
6. If possible, test against a JIRA instance to verify field mapping still works correctly with the abstraction layer

Scenarios tested

• All unit tests for field mapper functionality with generic field ID placeholders
• JIRA update command tests with refactored field ID handling
• Documentation examples reviewed for clarity and correctness

Deployment considerations

• This code change is ready for deployment on its own