feat: linting using changed-files gh action

[NamitBhutani]

What kind of change does this PR introduce?

Issue Number:

Fixes #1548

Did you add tests for your changes?

Snapshots/Videos:

If relevant, did you update the documentation?

Summary

Does this PR introduce a breaking change?

Other information

Have you read the contributing guide?

[github-actions]

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

1. The overall code coverage drops below the target threshold of the repository
2. Any file in the pull request has code coverage levels below the repository threshold
3. Merge conflicts

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

1. PRs with issues not assigned to you will be closed by the reviewer
2. Fix the first comment in the PR so that each issue listed automatically closes

Other

1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
2. Read the CONTRIBUTING.md file make

[NamitBhutani]

@palisadoes this method works, but we should wait for a bit before merging so that we are able to check against all changes to develop branch, them being - 1, someone else's commits getting merged in develop
2. Me merging updated develop in this branch

[palisadoes]

The files in this PR will not be applied to other PRs until this PR is merged.

I don't understand why we need to wait

[NamitBhutani]

The files in this PR will not be applied to other PRs until this PR is merged.

I don't understand why we need to wait

I wanted to wait so that we can test out all cases to prevent errors like before happening yet again.
But I guess it would be faster to recognise errors that way then, let's merge it then!

[palisadoes]

Please fix the failing test before I merge

[NamitBhutani]

Please fix the failing test before I merge

That failing test is the one I made on purpose, I just removed space from one of the files, I didn't change any code there.

[palisadoes]

Please fix it, so that we can see whether it passes as part of the approval process for the merge.

[NamitBhutani]

Please fix it, so that we can see whether it passes as part of the approval process for the merge.

Extremely sorry! I had gone to bed, rest assured those changes will not change how the api works.