README's CI/CD Pipeline section updated to reflect the current state.…

[JonathanLyles]

… Jest unit tests are required to pass before changes can be merged. ESLint and Prettier checks are non-blocking. They can be viewed in logs during code review

📝 Description

Brief description of what this PR does and why.

🧪 Testing

• All Jest tests pass locally (npm run test:unit)
• ESLint passes (npm run lint)
• [Errors not related to this update] Prettier formatting is applied (npm run format:check)
• [n/a] Manual testing completed for affected functionality
• Test coverage maintained or improved

📋 Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📝 Documentation update
• 🔧 Refactoring (no functional changes)
• 🧪 Test improvements

🔍 Changed Files

• README.md

⚡ Performance Impact

• No performance impact expected
• Performance improvements included
• Potential performance concerns (explain below)

🔒 Security Considerations

• No security implications
• Security review required
• Permissions/access changes included

📱 Salesforce Metadata

• No metadata changes
• Custom objects modified
• Permission sets updated
• Layouts/page layouts changed
• Validation rules added/modified

✅ Pre-Submission Checklist

• Code follows project coding standards
• Self-review of code completed
• Comments added for complex logic
• No console.log statements in production code
• All related documentation updated
• Salesforce metadata follows naming conventions

📸 Screenshots (if applicable)

🔗 Related Issues

• Closes #xxx
• Related to #xxx

🤝 Reviewer Notes

---

CI Pipeline Status: This PR will be automatically tested with Jest, ESLint, and Prettier checks. All status checks must pass before merging.