Issue Summary

Currently, duplicate Jira states are created after Jira Align Migration scripts are executed. It was identified In AgileCraft_Jira.cs (OnElapsedTimeBoards), we are calling FirstTimeSetupSteps which updates the boards regardless of whether it's active/not

Steps to Reproduce

1. Create a New Connector, add credentials, and test the connection. Don't Activate this connector.
2. After Jira Migration is completed, run the JA migration scripts for A_JiraStatus.csv
3. Check Jira Settings > State Mapping > Feature/Story

Expected Results

No duplicate state after the Jira Align migration.

Actual Results

Jira States are duplicated after Jira Align integration migration scripts are executed

Workaround

Do not enter the credentials on the new connector (Please note this will prevent support from testing the connectivity between JA <> Jira, prior to the actual migration)