Feature/DO-1834 Header Change Detection add HTTP status flags for custom behaviour for BigCommerce

[aaronmedina-dev]

---

Description of the proposed changes

• Update Aligent's Header Change Detection to accommodate BigCommerce checkout behavior
• Added props to have an ability to add custom HTTP statuses.
• Joined the URL Array to a single string before saving.

Screenshots (if applicable)
Before the change

After the Change
Test with added 406 status

Test without the 406

Other solutions considered (if any)

Notes to PR author

⚠️ Please make sure the changes adhere to the guidelines mentioned here

Notes to reviewers

🛈 When you've finished leaving feedback, please add a final comment to the PR tagging the author, letting them know that you have finished leaving feedback

[TheOrangePuff]

Looks good! Just a question and the Aikido recommendation needs review :)

[aaronmedina-dev]

Looks good! Just a question and the Aikido recommendation needs review :)

I think for our use case, this is not applicable? Our URLs are passed as props to the construct at deploy time and not at runtime, so there's no user input that would allow SSRF exploitation (?).
What do you think @TheOrangePuff ?