Fix sync issues with Slack and Jira

[davejones74]

Jira link

See PROJ-XXXXXX

Change description

• Improved local/dev startup reliability by fixing environment/config handling so the bot starts cleanly in both Node and Docker runs.
• Stabilized Docker experience by using a reachable base image and publishing container port 3000 to host (3000:3000) for working local health checks.
• Updated Application Insights configuration to support modern connection-string usage, keep backward compatibility, and safely skip telemetry when no valid key/connection string is set.
• Hardened Jira workflow transitions with fallback logic (use configured transition ID first, then resolve by available transition names) to prevent close/reopen failures.
• Strengthened Slack→Jira comment sync path with more resilient Jira ID extraction from Slack blocks plus better logging/diagnostics for event delivery and comment creation failures.

Testing done

Security Vulnerability Assessment

Created a Jira ticket from Slack, started ticket, changed ownership, added messages and resolved the ticket, checking Jira status on each step.

CVE Suppression: Are there any CVEs present in the codebase (either newly introduced or pre-existing) that are being intentionally suppressed or ignored by this commit?

• Yes
• No

Checklist

• commit messages are meaningful and follow good commit message guidelines
• README and other documentation has been updated / added (if needed)
• tests have been updated / new tests has been added (if needed)
• Does this PR introduce a breaking change