feat: add dependabot

[jamesxu123]

Tickets:

• HAC-34
• Dependabot? #702

List of changes:

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Type of change

Please delete options that are not relevant.

• 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)
• New release
• This change requires a documentation update

How has this been tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Test Configuration:

Firmware version:
Hardware:
Toolchain:
SDK:

Questions for code reviewers?

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• Listed change(s) in the Changelog
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have made corresponding changes to the documentation
• Any dependent changes have been merged and published in downstream modules

[krubenok]

Before merging this and letting Dependabot loose on at least a full year of stale dependencies, I'd suggest updating as many as you can in one shot first to give it a head start. Since it produces a PR for every single out of date dependency, it'll create a lot of noise we can solve faster+easier in one shot.

[krubenok]

There is a conversation to be had around weekly vs. daily. IMO - daily is fine if the Auto-merging Github Action I mentioned in the issue is implemented and we trust the CI/CD enough.

Edit: Issue #702

[jamesxu123]

I think the auto-merge is something to be explored and it would make things a lot easier. However, we're in the middle of making a lot of changes to the test suite to speed it up so it's probably safer if we go with weekly + manual review for now.

If everything goes well, making it automated would be a great future addition and I'll add it to the dev road map for the year.

[jamesxu123]

Before merging this and letting Dependabot loose on at least a full year of stale dependencies, I'd suggest updating as many as you can in one shot first to give it a head start. Since it produces a PR for every single out of date dependency, it'll create a lot of noise we can solve faster+easier in one shot.

Ran npm update and npm audit fix. There was a minor change with Sendgrid but it seems to be all good now after a quick fix.

[krubenok]

Should the auto-merging action be done at the same time, or do you want to leave that for later? Missed the other comment, sounds good.

Also, a similar setup should probably be implemented on the dashboard repo.