Context Navigation

Changes between Initial Version and Version 1 of Ticket #32933

initial	v1
1	1	Currently, the documentation points users to `Form.get_initial_for_field(field, field_name)` to get the initial data for a form field. However, I think it would be better to point users to `BoundField.initial`, e.g. using the pattern `form[field_name].initial`. (`BoundField.initial` should also be added to the [https://docs.djangoproject.com/en/3.2/ref/forms/api/#attributes-of-boundfield BoundField attribute documentation], as it seems to have been left out.)
2	2
3		There are a couple reasons I think users should be steered away from `get_initial_for_field()`. One reason is that ~~the~~ API is simpler because it doesn't require passing redundant `field` and `field_name` arguments. Another reason is that going through `BoundField` has the advantage of using the `BoundField` instance's cache, as `initial` is a cached property. (I'm going to be filing another ticket related to the latter difference, later.)
	3	There are a couple reasons I think users should be steered away from `get_initial_for_field()`. One reason is that `BoundField'`s API is simpler because it doesn't require passing redundant `field` and `field_name` arguments. Another reason is that going through `BoundField` has the advantage of using the `BoundField` instance's cache, as `initial` is a cached property. (I'm going to be filing another ticket related to the latter difference, later.)