refactor(rust): use explicit column lists

[MatthewLeboffe]

Current behavior

In this pr, SQL was introduced. Prior to our pull request, SELECT statements in our SQL queries were utilizing the * notation, which fetched all columns indiscriminately. This approach is considered bad practice and an issue was requested to use explicit columns in SELECT statements.

Fixes #6947

Proposed changes

To help prevent mistakes when using SQL queries, we can explicitly specify columns in every SELECT statement, significantly reducing the risk of errors.

Checks

• All commits in this Pull Request are signed and Verified by Github.
• All commits in this Pull Request follow the Ockam commit message convention.
• There are no Merge commits in this Pull Request. Ockam repo maintains a linear commit history. We merge Pull Requests by rebasing them onto the develop branch. Rebasing to the latest develop branch and force pushing to your Pull Request branch is okay.
• I have read and accept the Ockam Community Code of Conduct.
• I have read and accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam repository. The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a separate Pull Request, this will mark the commit as verified.

[mrinalwadhwa]

@MatthewLeboffe @Sweetsuro thank you for sending the PR.
Thank you for spending time on this, before we can merge could both of you, in 2 separate PRs, please

• Accept the Ockam Contributor License Agreement by adding your Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate new pull request to the build-trust/ockam repository.

The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a PR, this will mark the commit as verified.

[Sweetsuro]

Hi @mrinalwadhwa ! I believe we have already done so as a part of this PR, would you rather we have this done in separate in PRs?

[mrinalwadhwa]

Yes, they have to be 2 separate PRs - one for each of you, for our CI workflows to pick things up correctly. Sorry about the extra steps there.

[Sweetsuro]

Hi @mrinalwadhwa ! Now that both Matthew and I have accepted the clas, and that they are merged, is there anything else we need to do for this PR to be merged?

[etorreborre]

Everything looks good. Thanks for your contribution @MatthewLeboffe and @Sweetsuro!