Add code actions to generate doc comments

[sdankel]

Description

Closes #4571

Following the directory structure for code actions that was there before, I've added new modules for:

• function decls
• enum variants
• storage fields
• configurable constants

Following FuelLabs/sway-standards#5, the doc comment template is the same for all of these except for functions. For functions, the template includes the argument names & types, return value, and a generated example of usage which is just meant to be a starting point for the comment author.

For the basic template that most of these use, I created BasicDocCommentCodeAction. I also refactored some of the "generate impl" code actions that were there before into a trait called GenerateImplCodeAction to keep their common functionality separate from the "generate doc comment" code actions.

I updated the existing code action tests for enums & structs, and added a new one for functions. I didn't think it was necessary to test enum variants, storage fields, etc. since the template and underlying code is the same.

Example generating docs for a function

Checklist

• I have linked to any relevant issues.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation where relevant (API docs, the reference, and the Sway book).
• I have added tests that prove my fix is effective or that my feature works.
• I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
• I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
• I have requested a review from the relevant team or maintainers.

[bitzoic]

So cool!!!! I tried it out for enums, structs, functions, storage, and config blocks. Needless to say my mind was blown 🚀

I noticed that it doesn't give me the option to generate docs for function definitions within an ABI/interfaces. Will that be in another PR?

[JoshuaBatty]

Nice work @sdankel 🚀

Looks good.

[sdankel]

I noticed that it doesn't give me the option to generate docs for function definitions within an ABI/interfaces. Will that be in another PR?

Good catch! I will do that in a separate PR: #4645