feat(token registry): proto max collateral share

CHANGELOG.md

@@ -57,6 +57,7 @@ Ref: https://keepachangelog.com/en/1.0.0/
 - [913](https://github.com/umee-network/umee/pull/913) Changed update registry gov proposal to add and update tokens, but never delete them.
 - [918](https://github.com/umee-network/umee/pull/918) Add MarketSummary query to CLI.
 - [1068](https://github.com/umee-network/umee/pull/1068) Add a cache layer for token registry.
+- [1096](https://github.com/umee-network/umee/pull/1096) Add `max_collateral_supply` to the x/leverage token registry.
 - [1094](https://github.com/umee-network/umee/pull/1094) Added TotalCollateral query.
 
 ### Improvements

proto/umee/leverage/v1/leverage.proto

@@ -139,4 +139,13 @@ message Token {
   // and enable_borrow set to false. Such tokens can be safely removed from the
   // oracle and price feeder as well.
   bool blacklist = 14;
+
+  // Maximum collateral share specifies how much of the
+  // system's overall collateral be provided by a single token.
+  // Value is a percent; allowed values are in [0, 100] range.
+  // 100 means that the token has no restriction. 10 means maximum 10% of total
+  // collateral value can provided by this token.
+  uint32 max_collateral_share = 15 [
+    (gogoproto.moretags) = "yaml:\"max_collateral_supply\""
+  ];
 }