Automatic linting

[mrvisscher]

Checklist

• Keep pull requests small so they can be easily reviewed.
• Update the documentation, please follow the numpy style guide.
• Update tests.
• Categorize the PR by setting a good title and adding one of the labels:
  bug, feature, ui, change, documentation, breaking, ci
  as they show up in the changelog.
• Link this PR to related issues by using closing keywords.
• Add a milestone to the PR (and related issues, if any) for the intended release.
• Request a review from another developer.

[coveralls]

coverage: 56.101%. remained the same
when pulling 731fb91 on mrvisscher:ruff-linting
into ee24c15 on LCA-ActivityBrowser:main.

[coveralls]

coverage: 56.101%. remained the same
when pulling 5d5eefb on mrvisscher:ruff-linting
into ee24c15 on LCA-ActivityBrowser:main.

[coveralls]

coverage: 56.101%. remained the same
when pulling 3f47570 on mrvisscher:ruff-linting
into ee24c15 on LCA-ActivityBrowser:main.

[coveralls]

coverage: 56.101%. remained the same
when pulling 935b0a6 on mrvisscher:ruff-linting
into ee24c15 on LCA-ActivityBrowser:main.

[jsvgoncalves]

I would suggest adding a pre-commit [1] hook for ruff [2], to avoid wasting time (both from a devex and CI perspective).

[1] - https://pre-commit.com/
[2] - https://github.com/astral-sh/ruff-pre-commit?tab=readme-ov-file#using-ruff-with-pre-commit

[jsvgoncalves]

Suggested change

	with:
	args: check --fix

Probably don't want to fix on CI, but on the pre-commit hook maybe?

Btw it's a good idea to set your editor (and CI) to ensure files end with a \n [1].

[1] - https://stackoverflow.com/a/729795