fix: gho borrow cap and facilitator level checks [skip cypress]

[grothem]

General Changes

• Interface previously assumed the borrow cap was the facilitator level. A recent proposal set the GHO borrow cap, so theses changes take that value into account to calculate the maximum amount that is available to mint.

Developer Notes

Add any notes here that may be helpful for reviewers.

---

Author Checklist

Please ensure you, the author, have gone through this checklist to ensure there is an efficient workflow for the reviewers.

• The base branch is set to main
• The title is using Conventional Commit formatting
• The Github issue has been linked to the PR in the Development section
• The General Changes section has been filled out
• Developer Notes have been added (optional)

If the PR is ready for review:

• The PR is in Open state and not in Draft mode
• The Ready for Dev Review label has been added

Reviewer Checklist

Please ensure you, as the reviewer(s), have gone through this checklist to ensure that the code changes are ready to ship safely and to help mitigate any downstream issues that may occur.

• End-to-end tests are passing without any errors
• Code style generally follows existing patterns
• Code changes do not significantly increase the application bundle size
• If there are new 3rd-party packages, they do not introduce potential security threats
• If there are new environment variables being added, they have been added to the .env.example file as well as the pertinant .github/actions/* files
• There are no CI changes, or they have been approved by the DevOps and Engineering team(s)
• Code changes have been quality checked in the ephemeral URL
• QA verification has been completed
• There are two or more approvals from the core team
• Squash and merge has been checked

[height]

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

[github-actions]

• Ipfs hash: bafybeiaqxknk7hzbkfydgwnogv3i46nou2nbq2eb2frufwf5seozc23xxi
• Ipfs preview link: https://bafybeiaqxknk7hzbkfydgwnogv3i46nou2nbq2eb2frufwf5seozc23xxi.ipfs.cf-ipfs.com/

[github-actions]

📦 Next.js Bundle Analysis for aave-ui

This analysis was generated by the Next.js Bundle Analysis action. 🤖

⚠️ Global Bundle Size Increased

Page	Size (compressed)
global	573.5 KB (🟡 +99 B)

Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

Two Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load
/	43.62 KB (🟡 +1 B)	617.12 KB
/reserve-overview	15.37 KB (🟡 +2 B)	588.87 KB

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this.