docs: invalid use of Uri.https in readme

[Luckey-Elijah]

The README has the following snippet

@riverpod
Future<String> boredSuggestion(BoredSuggestionRef ref) async {
  final response = await http.get(
    Uri.https('https://boredapi.com/api/activity'),
  );
  final json = jsonDecode(response.body);
  return json['activity']! as String;
}

which is invalid use of Uri.https... likely should just be Uri.parse instead

@riverpod
Future<String> boredSuggestion(BoredSuggestionRef ref) async {
  final response = await http.get(
-   Uri.https('https://boredapi.com/api/activity'),
+   Uri.parse('https://boredapi.com/api/activity'),
  );
  final json = jsonDecode(response.body);
  return json['activity']! as String;
}

and the Bored-API used in the docs (and README) is down drewthoennes/Bored-API#83. I think it has been for about a month.

[Luckey-Elijah]

Okay i see #3645 covers issues with BoredAPI, updating this issue in a moment