chore: util to manage URLs in the codebase (#1179)

* chore: util to manage URLs in the codebase

* docs: mentiion validate_links and supported_versions in docs

* refactor: fix linter errors

docs/concepts/advanced/component_context_scope.md

@@ -53,8 +53,8 @@ This has two modes:
     you can access are a union of:
 
     - All the variables that were OUTSIDE the fill tag, including any\
-      [`{% with %}`](https://docs.djangoproject.com/en/5.1/ref/templates/builtins/#with) tags.
-    - Any loops ([`{% for ... %}`](https://docs.djangoproject.com/en/5.1/ref/templates/builtins/#cycle))
+      [`{% with %}`](https://docs.djangoproject.com/en/5.2/ref/templates/builtins/#with) tags.
+    - Any loops ([`{% for ... %}`](https://docs.djangoproject.com/en/5.2/ref/templates/builtins/#cycle))
       that the `{% fill %}` tag is part of.
     - Data returned from [`Component.get_template_data()`](../../../reference/api#django_components.Component.get_template_data)
       of the component that owns the fill tag.
@@ -67,7 +67,7 @@ This has two modes:
 
     Inside the [`{% fill %}`](../../../reference/template_tags#fill) tag, you can ONLY access variables from 2 places:
 
-    - Any loops ([`{% for ... %}`](https://docs.djangoproject.com/en/5.1/ref/templates/builtins/#cycle))
+    - Any loops ([`{% for ... %}`](https://docs.djangoproject.com/en/5.2/ref/templates/builtins/#cycle))
       that the `{% fill %}` tag is part of.
     - [`Component.get_template_data()`](../../../reference/api#django_components.Component.get_template_data)
       of the component which defined the template (AKA the "root" component).
@@ -177,5 +177,5 @@ But since `"cheese"` is not defined there, it's empty.
 
 !!! info
 
-    Notice that the variables defined with the [`{% with %}`](https://docs.djangoproject.com/en/5.1/ref/templates/builtins/#with)
+    Notice that the variables defined with the [`{% with %}`](https://docs.djangoproject.com/en/5.2/ref/templates/builtins/#with)
     tag are ignored inside the [`{% fill %}`](../../../reference/template_tags#fill) tag with the `"isolated"` mode.

docs/concepts/advanced/component_libraries.md

@@ -23,13 +23,13 @@ For live examples, see the [Community examples](../../overview/community.md#comm
         |--  mytags.py
     ```
 
-2.  Create custom [`Library`](https://docs.djangoproject.com/en/5.1/howto/custom-template-tags/#how-to-create-custom-template-tags-and-filters)
+2.  Create custom [`Library`](https://docs.djangoproject.com/en/5.2/howto/custom-template-tags/#how-to-create-custom-template-tags-and-filters)
     and [`ComponentRegistry`](django_components.component_registry.ComponentRegistry) instances in `mytags.py`
 
     This will be the entrypoint for using the components inside Django templates.
 
-    Remember that Django requires the [`Library`](https://docs.djangoproject.com/en/5.1/howto/custom-template-tags/#how-to-create-custom-template-tags-and-filters)
-    instance to be accessible under the `register` variable ([See Django docs](https://docs.djangoproject.com/en/dev/howto/custom-template-tags)):
+    Remember that Django requires the [`Library`](https://docs.djangoproject.com/en/5.2/howto/custom-template-tags/#how-to-create-custom-template-tags-and-filters)
+    instance to be accessible under the `register` variable ([See Django docs](https://docs.djangoproject.com/en/5.2/howto/custom-template-tags)):
 
     ```py
     from django.template import Library
@@ -148,7 +148,7 @@ For live examples, see the [Community examples](../../overview/community.md#comm
 
     Since you, as the library author, are not in control of the file system, it is recommended to load the components manually.
 
-    We recommend doing this in the [`AppConfig.ready()`](https://docs.djangoproject.com/en/5.1/ref/applications/#django.apps.AppConfig.ready)
+    We recommend doing this in the [`AppConfig.ready()`](https://docs.djangoproject.com/en/5.2/ref/applications/#django.apps.AppConfig.ready)
     hook of your `apps.py`:
 
     ```py
@@ -170,7 +170,7 @@ For live examples, see the [Community examples](../../overview/community.md#comm
     ```
 
     Note that you can also include any other startup logic within
-    [`AppConfig.ready()`](https://docs.djangoproject.com/en/5.1/ref/applications/#django.apps.AppConfig.ready).
+    [`AppConfig.ready()`](https://docs.djangoproject.com/en/5.2/ref/applications/#django.apps.AppConfig.ready).
 
 And that's it! The next step is to publish it.
 
@@ -185,7 +185,7 @@ django_components uses the [`build`](https://build.pypa.io/en/stable/) utility t
 python -m build --sdist --wheel --outdir dist/ .
 ```
 
-And to publish to PyPI, you can use [`twine`](https://docs.djangoproject.com/en/5.1/ref/applications/#django.apps.AppConfig.ready)
+And to publish to PyPI, you can use [`twine`](https://docs.djangoproject.com/en/5.2/ref/applications/#django.apps.AppConfig.ready)
 ([See Python user guide](https://packaging.python.org/en/latest/tutorials/packaging-projects/#uploading-the-distribution-archives))
 
 ```bash
@@ -219,7 +219,7 @@ After the package has been published, all that remains is to install it in other
     ]
     ```
 
-3. Optionally add the template tags to the [`builtins`](https://docs.djangoproject.com/en/5.1/topics/templates/#django.template.backends.django.DjangoTemplates),
+3. Optionally add the template tags to the [`builtins`](https://docs.djangoproject.com/en/5.2/topics/templates/#django.template.backends.django.DjangoTemplates),
    so you don't have to call `{% load mytags %}` in every template:
 
     ```python

docs/concepts/advanced/extensions.md

@@ -624,7 +624,7 @@ The help message prints out all the arguments and options available for the comm
 
 ### Testing Commands
 
-Commands can be tested using Django's [`call_command()`](https://docs.djangoproject.com/en/5.1/ref/django-admin/#running-management-commands-from-your-code)
+Commands can be tested using Django's [`call_command()`](https://docs.djangoproject.com/en/5.2/ref/django-admin/#running-management-commands-from-your-code)
 function, which allows you to simulate running the command in tests.
 
 ```python
@@ -699,8 +699,8 @@ class MyExtension(ComponentExtension):
 
     The [`URLRoute`](../../../reference/extension_urls#django_components.URLRoute) objects
     are different from objects created with Django's
-    [`django.urls.path()`](https://docs.djangoproject.com/en/5.1/ref/urls/#path).
-    Do NOT use `URLRoute` objects in Django's [`urlpatterns`](https://docs.djangoproject.com/en/5.1/topics/http/urls/#example)
+    [`django.urls.path()`](https://docs.djangoproject.com/en/5.2/ref/urls/#path).
+    Do NOT use `URLRoute` objects in Django's [`urlpatterns`](https://docs.djangoproject.com/en/5.2/topics/http/urls/#example)
     and vice versa!
 
     django-components uses a custom [`URLRoute`](../../../reference/extension_urls#django_components.URLRoute) class to define framework-agnostic routing rules.
@@ -758,7 +758,7 @@ The [`URLRoute`](../../../reference/extension_urls#django_components.URLRoute) c
 so that extensions could be used with non-Django frameworks in the future.
 
 However, that means that there may be some extra fields that Django's
-[`django.urls.path()`](https://docs.djangoproject.com/en/5.1/ref/urls/#path)
+[`django.urls.path()`](https://docs.djangoproject.com/en/5.2/ref/urls/#path)
 accepts, but which are not defined on the `URLRoute` object.
 
 To address this, the [`URLRoute`](../../../reference/extension_urls#django_components.URLRoute) object has

docs/concepts/advanced/provide_inject.md

@@ -82,7 +82,6 @@ class ChildComponent(Component):
         my_data = self.inject("my_data")
         print(my_data.hello)    # hi
         print(my_data.another)  # 123
-        return {}
 ```
 
 First argument to [`Component.inject()`](../../../reference/api/#django_components.Component.inject) is the _key_ (or _name_) of the provided data. This
@@ -97,7 +96,6 @@ class ChildComponent(Component):
     def get_template_data(self, args, kwargs, slots, context):
         my_data = self.inject("invalid_key", DEFAULT_DATA)
         assert my_data == DEFAULT_DATA
-        return {}
 ```
 
 !!! note

docs/concepts/advanced/rendering_js_css.md

@@ -109,8 +109,8 @@ fragment = MyComponent.render_to_response(deps_strategy="fragment")
 The `deps_strategy` parameter is set at the root of a component render tree, which is why it is not available for
 the [`{% component %}`](../../../reference/template_tags#component) tag.
 
-When you use Django's [`django.shortcuts.render()`](https://docs.djangoproject.com/en/5.1/topics/http/shortcuts/#render)
-or [`Template.render()`](https://docs.djangoproject.com/en/5.1/ref/templates/api/#django.template.Template.render) to render templates,
+When you use Django's [`django.shortcuts.render()`](https://docs.djangoproject.com/en/5.2/topics/http/shortcuts/#render)
+or [`Template.render()`](https://docs.djangoproject.com/en/5.2/ref/templates/api/#django.template.Template.render) to render templates,
 you can't directly set the `deps_strategy` parameter.
 
 In this case, you can set the `deps_strategy` with the `DJC_DEPS_STRATEGY` context variable.
@@ -351,8 +351,8 @@ or templates can be rendered:
 
 -  [`Component.render()`](../../../reference/api/#django_components.Component.render)
 -  [`Component.render_to_response()`](../../../reference/api/#django_components.Component.render_to_response)
--  [`Template.render()`](https://docs.djangoproject.com/en/5.1/ref/templates/api/#django.template.Template.render)
--  [`django.shortcuts.render()`](https://docs.djangoproject.com/en/5.1/topics/http/shortcuts/#render)
+-  [`Template.render()`](https://docs.djangoproject.com/en/5.2/ref/templates/api/#django.template.Template.render)
+-  [`django.shortcuts.render()`](https://docs.djangoproject.com/en/5.2/topics/http/shortcuts/#render)
 
 This way you don't need to manually handle rendering of JS / CSS.