Add Custom Properties for Repository-Derived Tables

[Recurzion]

This PR adds the ability to query repository custom properties (returned as jsonb) for any repository-derived columns via sharedRepositoryColumns() and updates docs with example queries (these can be removed if not needed).

Teams often use GitHub custom properties to capture custom repo-level metadata/attributes, so adding this field should benefit organizations that leverage it.

This applies to the following tables:

• github_repository
• github_my_repository
• github_team_repository
• github_search_repository
• and any other table using sharedRepositoryColumns()

Example query results

Results

select name,custom_properties  from github_my_repository where name = 'myrepo'

+----------+-------------------------------+
| name | custom_properties                 |
+----------+-------------------------------+
|myrepo |  {"key1":"value1","key2":"value2"}
+----------+-------------------------------+

select name,custom_properties -> 'myproperty' as myproperty from github_repository where  full_name = 'myorg/myrepo'

+----------+-------+
| name | myproperty|
+----------+-------+
|myrepo | "myvalue"|
+----------+-------+

[cbruno10]

@Recurzion Thanks for the PR!

I've added a couple suggestions, the bigger one is around moving from v3 (REST) to v4 (GraphQL) API, happy to discuss more if you have any questions. Thanks!

[cbruno10]

Instead of using the v3 RESTful API, can we retrieve it using the newer GraphQL API, similar to most other columns in this table? GraphQL APIs in general are more forgiving with rate limits and from what we could see, better supported moving forward.

In the GraphQL API, the Repository object has repositoryCustomPropertyValues, so we can use that I believe and we should get the first: 100, as there seems to be a limit of 100 property definitions.

You can look at the labels column in the github_issue table, as it has the same shape and also does an array to map conversion like this property would use.

[Recurzion]

Sure thing. I followed the same pattern used by the labels column now.