DBC22-6524: removed debugging console logs and warnings as possible

[bcgov-brwang]

📝 Submitter

🔗 JIRA Ticket

• Ticket Link: https://moti-imb.atlassian.net/browse/DBC22-6524

---

✅ Quality Assurance & Requirements

• Requirements Met: I have confirmed that all acceptance criteria from the JIRA ticket are fulfilled.
• Tested desktop in local or dev envs
• Tested mobile in local or dev envs
• Ran unit tests locally
• SonarCloud: I have verified that the SonarCloud analysis is clean/passing for this branch.

⚙️ Configuration & Environment

• New Env Variables: Does this PR require new environment variables? (Yes/No)

  If yes, please list them here and ensure they are added to secret manager, the .env.example. and the Vault by an STA.

🧪 How to Test (if required)

1. Deploy to dev.
2. Login to https://dev.drivebc.ca/drivebc-cms/.
3. Create/Edit an advisory and save to draft or publish.
4. Verify the advisory can be saved or published successfully without 500 server errors.

---

🔍 Reviewer Checklist

• Reviewed code for logic and cleanliness
• Re-tested desktop/mobile in local or dev envs
• Verified no new console warnings/errors
• Confirmed that any new env variables are understood/documented

[wmuldergov]

I am still getting an error when I start an advisory, but I think that is because you cannot save an advisory without a polygon. One you have a polygon set, then the errors go away.
Is there a way to add logic that autosave doesn't require the polygon to work?

[wmuldergov]

While autosave is fixed...now I am able to publish an advisory without a polygon. I believe we should not be allowing users to publish without a polygon set.