Add Feature To Optionally Limit ID Reuse in Timing Model

[davidbiancolin]

Resolves #643, by adding a UserYanker internally to the timing model. This can be optionally disabled in timing models where it safe to have transactions under the same ID in flight.

This crashes in elaboration, since the output FIRRTL is malformed.

• TODO: do not emit when max flight is capped already to 1 in the target.

Related PRs / Issues

#643

UI / API Impact

New parameter added to FASEDTiming models.

Verilog / AGFI Compatibility

Needs AGFI regeneration.

Contributor Checklist

• Did you set dev as the base branch?
• Did you add Scaladoc to every public function/method?
• Did you add at least one test demonstrating the PR?
• Did you delete any extraneous prints/debugging code?
• Did you state the UI / API impact?
• Did you specify the Verilog / AGFI compatibility impact?

• (If applicable) Did you regenerate and publicly share default AGFIs?

• (If applicable) Did you mark the PR as "Please Backport"?
• (On merge) Did you update release notes in the dev-to-master PR ?

Reviewer Checklist (only modified by reviewer)

• Did you mark the proper release milestone?
• Did you check whether all relevant Contributor checkboxes have been checked?

[davidbiancolin]

@Mergifyio rebase

[mergify]

rebase

✅ Branch has been successfully rebased

[davidbiancolin]

@Mergifyio rebase

[mergify]

rebase

✅ Branch has been successfully rebased

[davidbiancolin]

@Mergifyio rebase

[mergify]

rebase

☑️ Nothing to do

• -closed [:pushpin: rebase requirement]
• #commits-behind>0 [:pushpin: rebase requirement]