Populate null columns in repo_info table

[guptapratykshh]

Description
added data collection for six null columns in repo_info table -contributing_file, security_issue_file, changelog_file, keywords, pull_requests_enabled, and pages_enabled.

This PR fixes #2675

Notes for Reviewers

Signed commits

• Yes, I signed my commits.

[sgoggins]

I would like to see Unit tests written for these functions in a way that validates the existence of the end point and incorporates the use of edge cases. i.e. valid cases with an empty URL, invalid cases where there is not a 404 but its empty, etc.).

[sgoggins]

We are not using the .get syntax elsewhere. I am not sure I love the nesting, and I agree it is useful to get these data elements we previously ignored.

Can you share a rationale for this design choice?

[MoralCode]

get syntax is better because it wont crash if the key doesnt exist (will return a default value, which is none by default)

I use it all the time

[MoralCode]

I would like to see Unit tests written for these functions in a way that validates the existence of the end point and incorporates the use of edge cases. i.e. valid cases with an empty URL, invalid cases where there is not a 404 but its empty, etc.).

Unit tests for API dependent stuff is... a little trickier to do. especially if the function being tested is making the web calls on its own, not expecting the data to be passed into them.

[MoralCode]

This will also conflict with #3597. Im going to say that this should wait for that PR to merge, and then be adjusted to reuse the same function for fetching the correct domain name to use in Github API calls.

[MoralCode]

Hello! Just wanted to check in to see if you were still interested in helping the maintainers merge this PR. We noticed it has been a little while since this last had activity, and are considering closing it or taking it over if it remains in its current state.

Please react to or reply to this to confirm your interest in the next 7 days or let us know if you are no longer interested in this so we can best prioritize everyone's contributions.

Thanks!