[Lambda] Display vCPU Allocation

### 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 "me too" comments, 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

**Tell us about your request**
Provide a visual representation of the vCPU allocation for a Lambda function based on its configured memory size.

**Which service(s) is this request for?**
AWS Lambda

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Currently, the amount of vCPU allocated to a Lambda function is proportional to the memory configuration, as described in the [AWS Lambda documentation](https://docs.aws.amazon.com/lambda/latest/dg/configuration-memory.html). However, this information is not visually displayed in the AWS console, which can lead to misunderstandings among developers and management teams.

For example, while experienced AWS developers may understand this relationship, managers or supervisors might misinterpret memory usage and suggest reducing memory allocation without realizing the impact on vCPU performance. This can result in slower execution times and increased costs.

A visual indicator, such as a progress bar or percentage display showing the vCPU allocation (e.g., full vCPU at 1,769 MB), would improve clarity for all stakeholders. It would facilitate discussions with management, enhance developers' understanding, and reduce incorrect optimization actions.

**Are you currently working around this issue?**
To address this, we rely on documentation and tools like [Epsagon's Lambda Memory Performance Benchmark](https://github.com/epsagon/lambda-memory-performance-benchmark) to validate the relationship between memory and vCPU allocation. However, these methods require additional effort and are not integrated into the AWS console.

**Additional context**
This feature would align with AWS's goal of providing intuitive and transparent tools for developers and organizations. It would also reduce the need for external tools and documentation references, streamlining the optimization process for Lambda functions.

**Attachments**
N/A