Feat: Allow non-legacy access to all get AVS routes

[gowthamsundaresan]

The flag legacy = 'true' | 'false' has been added to the following routes

GET /avs
GET /avs/:address
GET /avs/:address/stakers
GET /avs/:address/operators

Calling any of these routes with the flag set to false (eg: GET /avs?legacy=false) will filter AVSs using the the settings made via area-internal-dashboard looking for isVisible === true && isVerified === true from the AdditionalInfo table. Fallback to the CuratedMetadata table remains in case these fields were never created.

Consider using ?legacy=false for area-app immediately, and then once we are happy with the usage of area-internal-dashboard, updating the AvsFilterQuery to use AdditionalInfo and deprecating CuratedMetadata altogether -- this would allow ee-ui to be in sync with area-app

Note: No breaking changes