Remove force option on snowplow event generation

What does this MR do and why?

• updates the docs to remove implying that the category and action are used for event file name uniqueness - the timestamp does that more than anything else.
• remove force option for the generator as this is now a contrived need since timestamp makes the file almost impossible to need this option.
  • there is more probability that duplicate event files will be created due to use of timestamp and that should likely be handled in someway in the future.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #393223 (closed)