feat: add submodule description

[jor2]

Description

#29

Release required?

• No release
• Patch release (x.x.X)
• Minor release (x.X.x)
• Major release (X.x.x)

Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

• If relevant, a test for the change is included or updated with this PR.
• If relevant, documentation for the change is included or updated with this PR.

For mergers

• Use a conventional commit message to set the release level. Follow the guidelines.
• Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
• Use the Squash and merge option.

[daniel-butler-irl]

/run pipeline

[jor2]

/run pipeline

[vburckhardt]

@jor2 @daniel-butler-irl - could we just test out and validate that llm won't get confused with submodules wrt the instructions at https://github.com/terraform-ibm-modules/tim-mcp/blob/main/static/instructions.md . any ambiguity or inconsistency in looking up details (currently using module id) would reduce in degraded results.

[jor2]

/run pipeline

[terraform-ibm-modules-ops]

🎉 This PR is included in version 1.8.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀