Update linting process and repair CI

[mcopik]

We drop flake8-black because it has not been updated in a long time, and it kept our CI permanently broken. We also fixed .gitignore, since we were not linting cache.py and regression.py.

Summary by CodeRabbit

• Chores
  • Integrated an automated formatting check with the Black linter into the continuous integration process.
  • Updated configuration settings for managing ignored files and streamlining dependency management.
• Style
  • Applied multiple internal formatting and readability improvements to enhance code consistency and maintainability.

[coderabbitai]

Walkthrough

This pull request enhances code quality and consistency by integrating a Black linter check into the CI pipeline and updating the linting script. It also refines file ignore patterns and dependency management. Several modules in the project have been reformatted for improved readability, including adjustments to function signatures and string formatting. These changes do not alter functionality but aim to ensure a more streamlined and maintainable codebase.

Changes

Files	Change Summary
.circleci/config.yml, tools/linting.py	Added a new CI step to run the Black linter in check mode and simplified the flake8 command for linting.
.gitignore, requirements.txt	Updated ignore patterns for regression and cache-related files in .gitignore and removed the flake8-black package from requirements.txt.
sebs/aws/aws.py, sebs/cache.py, sebs/gcp/gcp.py, sebs/openwhisk/openwhisk.py, sebs/regression.py	Reformatted function signatures and string constructions (e.g., adding spaces after commas, vertical alignment of parameters and arguments, and consolidating multi-line strings) for improved readability.

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer
    participant CI as CircleCI
    participant Lint as Linting Script

    Dev->>CI: Push commit with changes
    CI->>Lint: Trigger linting job
    Lint->>Lint: Activate Python virtual environment
    Lint->>Lint: Run Black in check mode on 'sebs' directory using .black.toml
    Lint->>Lint: Execute flake8 linting
    Lint->>CI: Return linting results
    CI->>Dev: Report job status

Loading

Poem

I'm a little rabbit, hopping through the code,
Formatting and linting light my humble abode.
Black and flake8 now dance in a neat parade,
With tidy lines and comments perfectly laid.
In every nibble of bytes, my heart happily explodes!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e662eb5 and 02e0807.

📒 Files selected for processing (1)

• .circleci/config.yml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• .circleci/config.yml

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.