rsconnect-python crashes on rsconnect list when server has null name

[ChaitaC]

Issue
The rsconnect list command crashes with TypeError: '<' not supported between instances of 'str' and 'NoneType' when a server entry has a null/None value for its name field.
Re Slack thread: https://positpbc.slack.com/archives/CCD5REGR4/p1756228912248909

Reproduction Steps

1. Create or modify the servers.json file with a null name:
   echo '{"bad_server": {"url": "https://example.com", "name": null}}' > ~/.rsconnect-python/servers.json
2. Run rsconnect list
3. Observe the crash with TypeError

FROM Claude:

The _get_sorted_values() method in metadata.py uses Python's sorted() function without handling the case where some values might be None. When
sorting server entries by name, any entry with a null name will cause the sort comparison to fail.

Suggested Fix

Apply one of these solutions:

1. Handle None values in the sort key:
   In get_all_servers()
   return self._get_sorted_values(lambda s: s["name"] or "")

2. Add defensive handling in _get_sorted_values:
   def _get_sorted_values(self, sort_by):
   def safe_sort(item):
   key = sort_by(item)
   return key if key is not None else ""
   return sorted(self._data.values(), key=safe_sort)

Additional Notes

• This likely happens when server entries are manually edited or created with a null name
• The set() method should validate that the name is not None before storing
• Consider adding validation elsewhere to prevent null values in required fields

[ChaitaC]

Before implementing the fix, we should confirm with the user if:

1. They checked whether any server entries have "name": null or are missing the name field entirely
2. If they can examine their ~/.rsconnect-python/servers.json file to verify this theory

If they find no evidence of null/missing names, we should investigate alternative causes for this TypeError, as our reproduction case might not match their exact scenario.

@brooklynbagel Even though I was able to reproduce the issue by creating an empty server entry with "name": null, I want to make sure that no other edge cases are causing similar symptoms before we try to fix this.