feat: Added glue table indexes

[amanenk]

Summary

closes #1368
closes #1366

---

Use the following steps to ensure your PR is ready to be reviewed

• Read the contribution guidelines 🧑‍🎓
• Run go fmt to format your code 🖊
• Lint your changes via golangci-lint run 🚨 (install golangci-lint here)
• Update or add tests. Learn more about testing here 🧪
• Update the docs by running go run ./docs/docs.go and committing the changes 📃
• If adding a new resource, add relevant Terraform files in a separate PR 📂
• Ensure the status checks below are successful ✅

[disq]

Maybe add a unit test just for the resolver? The documentation (godoc) for the method needs more clarification or examples as well.

[bbernays]

I like the resolver you added in this PR... My question looking at these fields is whether this is going to fetch too much data... as all of the nested calls are going to happen sequentially.... And looking at the Index/Partition data it doesn't seem that compliance/ security focused...

[amanenk]

I like the resolver you added in this PR... My question looking at these fields is whether this is going to fetch too much data... as all of the nested calls are going to happen sequentially.... And looking at the Index/Partition data it doesn't seem that compliance/ security focused...

@bbernays Agree on partitions. I have removed them. I have left indexes because it is infrastructural data that does not depend on data that is "fed" to glue