aws_vpc_endpoint resource schema outdated

### Extension Version

v2.34.3

### VS Code Version

Version: 1.98.2 (Universal)
Commit: ddc367ed5c8936efe395cffeec279b04ffd7db78
Date: 2025-03-12T13:32:45.399Z
Electron: 34.2.0
ElectronBuildId: 11161602
Chromium: 132.0.6834.196
Node.js: 20.18.2
V8: 13.2.152.36-electron.0
OS: Darwin x64 22.6.0

### Operating System

macOS 13.7.4 (22H420)

### Terraform Version

Terraform v1.11.2 on darwin_amd64

### Steps to Reproduce

resource "aws_vpc_endpoint" shows an error , because "An attribute named "service_name" is required here"
And at the same time "An attribute named "resource_configuration_arn" is not expected here"

That is in correct, resource can have either of them

### Expected Behavior

extension should understand new resource configuration

Alternatively, maybe it can download latest aws provider and use an updated schema?

### Actual Behavior

Shows errors

### Terraform Configuration

```terraform
resource "aws_vpc_endpoint" "example" {
resource_configuration_arn = aws_vpclattice_resource_configuration.example.arn
subnet_ids = [aws_subnet.example.id]
vpc_endpoint_type = "Resource"
vpc_id = aws_vpc.example.id
}
```

### Project Structure

```sh

```

### Gist

_No response_

### Anything Else?

_No response_

### Workarounds

_No response_

### References

_No response_

### Help Wanted

- [ ] I'm interested in contributing a fix myself

### Community Note

- Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment

Start by locating the TypeScript code that validates the aws_vpc_endpoint resource and how the extension obtains Terraform provider schemas. Reproduce the diagnostics with the configuration in the issue, then compare the accepted attributes with the current AWS provider schema. Done means resource_configuration_arn is accepted as an alternative to service_name without incorrectly flagging either attribute.

Written by the indexing model from the issue text.