docs: update linting results URL and add interactive linter link (#4771)

Updated the documentation for new data contributors to use HTTPS for the
linting results API, format the URL in a code block, and mention the
interactive linter page at test.osv.dev/linter.

---
*PR created automatically by Jules for task
[12511192143355548851](https://jules.google.com/task/12511192143355548851)
started by @another-rex*

---------

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
Co-authored-by: Xueqin Cui <72771658+cuixq@users.noreply.github.com>

Author: 3 people

docs/new_source.md

@@ -25,7 +25,11 @@ The step by step instructions are as follows:
 
 - [ ] Create a PR to start [importing the records you are publishing into our test instance of OSV.dev](https://github.com/google/osv.dev/blob/master/source_test.yaml) and validate everything is working as intended there.
 
-- [ ] After successful import, review the OSV-linter results by querying http://api.test.osv.dev/v1experimental/importfindings/{source_name} to identify and address any important record linting issues (allow up to a 1-day delay).
+- [ ] After successful import, review the OSV-linter results by querying:
+  ```
+  https://api.test.osv.dev/v1experimental/importfindings/{source_name}
+  ```
+  to identify and address any important record linting issues. Note that it may take up to 24 hours for new findings to populate. You can also view this information more interactively at [test.osv.dev/linter](https://test.osv.dev/linter).
 
 - [ ] Create a PR to start [importing the records you are publishing into our production environment](https://github.com/google/osv.dev/blob/master/source.yaml)