Allow setting the default resource options in scope

[AdmiringWorm]

Is your feature request related to a problem? Please describe.
Instead of needing to set the different options again and again for every localize tag, a scoped tag for setting default options would be useful.

Describe the solution you'd like
The solution would be something similar to:

<localize-options resource-name="Common" html="true">
  <p localize>
    <a href="https://google.com">Test</a>
  </p>
</localize-options>

These should also be able to be nested, and overridden when necessary (This would also then need to allow the ability to ignore these settings when necessary).

[issue-label-bot]

Issue-Label Bot is automatically applying the label Feature to this issue, with a confidence of 0.99. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[AdmiringWorm]

Still being worked on.

Expected to use <localize-scope> as the tag helper name instead of <localize-options>.

This is not guaranteed as I am also considering changing elements and attributes to have loc- as a prefix (in the case of <localize> element, that would be changed to <loc> and most likely removing the localize attribute (or make it optional if other attributes are used).)
This is not been decided yet though.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.