docs: update template to callout implementation areas (#1197)

* docs: update template to callout implementation areas

Add more guidance for FIP authors/implementers to think through the full set of repos that will need to update to fully land the FIP.  This is done to help avoid the case of thinking a FIP is "done" because part of the work is complete (e.g., a builtin-actors change), when in fact there are other areas that need to be updated as well.

* Fix formatting and grammar in template.md

Author: BigLep

templates/template.md

@@ -67,6 +67,8 @@ All FIPs must contain a section that discusses the product implications/consider
 <!--The implementations must be completed before any core FIP is given status "Final", but it need not be completed before the FIP is accepted. While there is merit to the approach of reaching consensus on the specification and rationale before writing code, the principle of "rough consensus and running code" is still useful when it comes to resolving many discussions of API details.-->
 The implementations must be completed before any core FIP is given status "Final", but it need not be completed before the FIP is accepted. While there is merit to the approach of reaching consensus on the specification and rationale before writing code, the principle of "rough consensus and running code" is still useful when it comes to resolving many discussions of API details.
 
+List out the tracking issue(s) or PR(s) that will need to be completed for this to land and become "Final".  If there isn't a tracking issue/PR yet, at least list the repo(s) that will need work.  For example, does a builtin-actors change also requires changes in a node implementation like Lotus (either for verfication purposes or to adjust for the protocol change)?  Some example repos to consider: builtin-actors, ref-fvm, rust-fil-proofs, lotus, forest, venus, curio.
+
 ## TODO
 <!--A section that lists any unresolved issues or tasks that are part of the FIP proposal. Examples of these include performing benchmarking to know gas fees, validate claims made in the FIP once the final implementation is ready, etc. A FIP can only move to a “Last Call” status once all these items have been resolved.-->
 A section that lists any unresolved issues or tasks that are part of the FIP proposal. Examples of these include performing benchmarking to know gas fees, validate claims made in the FIP once the final implementation is ready, etc. A FIP can only move to a “Last Call” status once all these items have been resolved.