feat: slack bot for uni

[HenriqueSFernandes]

Closes #1691

Custom Slack bot that notifies when a new Flutter version is available.

[codecov[bot]]

Codecov Report

:white_check_mark: All modified and coverable lines are covered by tests. :white_check_mark: Project coverage is 60%. Comparing base (7d9c4e8) to head (3d20f15). :warning: Report is 102 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff           @@
##           develop   #1737   +/-   ##
=======================================
  Coverage       60%     60%           
=======================================
  Files            2       2           
  Lines           81      81           
=======================================
  Hits            48      48           
  Misses          33      33           

:rocket: New features to boost your workflow:

• :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[pedroafmonteiro]

@limwa we could change the deploy action to not get activated by changes on the uni_bot package, because creating a single repo only for this simple bot is a bit much in my opinion and the bot is directly connected to the app so I don't think it is that big of a problem to be together with the rest of the codebase, what do you think?

[limwa]

My opinion still stands... If a different repo is too much, then a different top-level folder should still be used. But why?

The reason the uni packages are in the packages folder is because they are a pub workspace (as declared in the top-level pubspec.yaml). This is a pub (dart's package manager) feature that allows separate packages to depend on each other without having to publish them. The reason they were moved into the packages folder was to convey that all of those packages should be declared in pubspec.yaml.

Now, you're adding a Node.js package to that packages folder and the meaning of the packages folder is lost. This bot does not depend on any of the other packages declared in the workspace and, therefore, there is no reason to justify that it is more useful for it to be added to the packages folder than to a new top-level folder...

Furthermore, Node.js also has its own set of tools to manage "workspaces" and, with the current layout, it will be very hard to use that, if need be, in the future.

As I said, my opinion still stands and my arguments are laid out here. You're free to continue as is, it's just my recommendation 😅

[pedroafmonteiro]

Yeah, I agree with this! We will maybe go for the top-level folder option. @HenriqueSFernandes could you maybe move the codebase of the bot to a folder in the root of the repo? For example, a folder named tools would be nice to represent things that help uni but are externally related to it. What do you think?

[pedroafmonteiro]

Closed via another repo: https://github.com/NIAEFEUP/nibots