Improvements on Verida Auth API

[aurelticot]

• Provide record metadata properties on Auth Token records (particularly the built-in creation date insertedAt)
  • Also, nice to have but not required would be a "last used date"
• Support pagination when querying the tokens list, also sorted by creation date (insertedAt)
• Support filtering when querying the tokens list (same as generic database/datastore query)
• Allow passing a label for when users manually create new authorizations. As there is no linked application (appDID), there is no identifiable details for this token other than its scopes (and creation date)
• Better structured information in scope definitions as it's displayed to the end-user when creating a new authorization
  • Particularly for the data scopes as there's a mix of database name vs base64 schema url, and the three operations (r, w, d) that make it difficult to work with in the UI
  • Ideally We should find a harmonised way to present the scope between /auth/scopes and /auth/resolve-scopes
• Optimise auth token generation for the same application?
  • A new token is generated for every auth request, but when it comes from the same appDID maybe we could find a way to optimise it. See Re-use auth token for apps #230